Screen vulnerabilitiesRanked by how likely they are to be used.

Product30 versions
The short answer

Screen is made by Gnu. We track 9 published vulnerabilities in it, across 30 versions. None of them is on the list of flaws known to be exploited today. If you run Screen, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Screen vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Screen's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Screen flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 9.1%

    encoding.c in GNU Screen through 4.8.0 allows remote attackers to cause a denial of service (invalid write access and application crash) or possibly have unspecified other impact via a crafted UTF-8 character sequence.

    CVSS9.8Published9 Feb 2021
  2. 3.4%

    Integer signedness error in ansi.c for GNU screen 4.0.1 and earlier, and 3.9.15 and earlier, allows local users to execute arbitrary code via a large number of ";" (semicolon) characters in escape sequences, which...

    CVSS10.0Published15 Dec 2003
  3. 2.6%

    A buffer overflow was found in the way GNU Screen before 4.8.0 treated the special escape OSC 49.

    CVSS9.8Published24 Feb 2020
  4. 2.1%

    Multiple unspecified vulnerabilities in the "utf8 combining characters handling" (utf8_handle_comb function in encoding.c) in screen before 4.0.3 allows user-assisted attackers to cause a denial of service (crash or...

    CVSS2.6Published24 Oct 2006
  5. 1.3%

    Buffer overflow in the Braille module for GNU screen 3.9.11, when HAVE_BRAILLE is defined, allows local users to execute arbitrary code.

    CVSS4.6Published23 Apr 2002
  6. 1.1%

    GNU screen before 4.5.1 allows local users to modify arbitrary files and consequently gain root privileges by leveraging improper checking of logfile permissions.

    CVSS7.8Published20 Mar 2017
  7. 0.7%

    GNU screen 4.0.3 allows local users to unlock the screen via a CTRL-C sequence at the password prompt.

    CVSS7.2Published5 Jun 2007
  8. 0.5%

    socket.c in GNU Screen through 4.9.0, when installed setuid or setgid (the default on platforms such as Arch Linux and FreeBSD), allows local users to send a privileged SIGHUP signal to any PID, causing a denial of...

    CVSS6.5Published8 Apr 2023
  9. 0.3%

    GNU screen 4.0.3 creates the /tmp/screen-exchange temporary file with world-readable permissions, which might allow local users to obtain sensitive session information.

    CVSS4.9Published1 Apr 2009
EdgeProtect

Running Screen? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 9 published vulnerabilities listed under the name Screen, across 30 versions.

None of Screen's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Screen. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.