Skip to content
Fencer Intel
medium 5.0

CVE-2009-4496 json

Boa 0.94.14rc21 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a windo…

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

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

Summary

Boa 0.94.14rc21 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.

Is CVE-2009-4496 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-4496 updated

boa: sanitize nonprintable characters in error logs

  • 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-33504)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-33504 BOA Web Server 0.94.x - 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 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

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.