Skip to content
Fencer Intel
medium 6.8

CVE-2009-4487 json

nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's…

published 16y ago modified 4mo ago also EUVD-2009-4454

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
26.8%
EPSS 26.8% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.

Patch / fix

Is CVE-2009-4487 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-4487 updated cvss 2.6

nginx: Absent sanitation of escape sequences in web server log

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-33490)
  2. Published

Exploit prediction

26.82% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-33490 Nginx 0.7.64 - Terminal Escape Sequence in Logs Command Injection remote, 2010-01-11
  • ush.it http://www.ush.it/team/ush/hack_httpd_escape/adv.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.