CVE-2009-4496 is a log escape-sequence injection in the Boa web server 0.94.14rc21: Boa writes request data to its log without filtering non-printable characters, so an escape sequence in a request runs in the terminal of whoever reads the log. NVD scores it 5.0 under CVSS v2. There is no upstream fix.
Vulnerability summary
CVSS base score
5
Medium severity
EPSS score (FIRST)
12.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2009-4496 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Boa web server | cpe:2.3:a:boa:boa:0.94.14rc21:*:*:*:*:*:*:* | 0.94.14rc21 (NVD; the ush.it advisory adds 'probably earlier versions'); no fixed upstream release |
What does this mean for affected devices?
NVD's description: "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." NVD's Primary score is CVSS v2 5.0 (AV:N/AC:L/Au:N/C:P/I:N/A:N) with CWE-20; the record has no CVSS v3 score. The CPE configuration lists Boa 0.94.14rc21 only. The record was published on 2010-01-13 (NVD).
How does the injection work?
The ush.it advisory of 2010-01-10 by Giovanni Pellerano, Alessandro Tanasi and Francesco Ongaro covers ten web servers, Boa among them. It explains that when "the logfiles are viewed with tools like "cat" or "tail" such control chars reach the terminal and are executed", and its proof of concept for Boa is a single request for a URL-encoded ESC ] 2 ; owned BEL sequence, which sets the terminal title. In the 0.94.14rc21 source from the Boa home page, log_access() prints the request line, Referer and User-Agent with printf() and does not filter control characters. The advisory records Boa's vendor response as "NO-RESPONSE".
Why does a 2010 Boa CVE still matter on devices?
Because Boa is still inside device SDKs. The Boa home page was last updated on 23 February 2005, and its newest builds are 0.94.13 (release) and 0.94.14rc21 (development). Microsoft Threat Intelligence's November 2022 report on Boa says that "despite being discontinued in 2005, the Boa web server continues to be implemented by different vendors across a variety of IoT devices and popular software development kits (SDKs)", counted over 1 million Internet-exposed Boa server components in one week, and names CVE-2009-4496 among Boa's known vulnerabilities. It also notes that Realtek SDK updates "do not include patches for Boa vulnerabilities"; the Realtek SDK web server flaw CVE-2021-35395 is one such SDK issue. Our embedded web server firmware guide explains how to find Boa in an image from its Boa/0.94.14rc21 Server string.
How do you fix or mitigate it?
No upstream release exists, so the device maker patches its own copy: replace or escape non-printable bytes before Boa writes request fields to the access and error logs, or move the product to a maintained web server. Until then, read device logs with a tool that shows control characters instead of passing them to the terminal, such as cat -v or less without -r. The other Boa CVEs need different handling: CVE-2017-9833 and CVE-2021-33558 are in vendor files on top of Boa, not in Boa's own code.
CVE-2009-4496 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.12403, the 96th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: Boa 0.94.14rc21 writes data to a log file without sanitizing non-printable characters, terminal escape sequence; Primary CVSS v2 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N; no v3; CWE-20; CPE boa 0.94.14rc21; published 2010-01-13. — NVD
- ush.it advisory (2010-01-10): log escape sequence injection in ten servers including Boa 0.94.14rc21 ('and probably earlier versions'); PoC curl of %1b%5d%32%3b%6f%77%6e%65%64%07%0a; Boa vendor response NO-RESPONSE. — ush.it
- Boa home page: news last updated 23 February 2005; latest released version 0.94.13; latest development version 0.94.14rc21. boa-0.94.14rc21 src/log.c log_access() printf of logline, referer and user agent without filtering. — Boa project
- Microsoft Threat Intelligence (2022-11-22, updated 2022-12-08): Boa discontinued in 2005 yet implemented across IoT devices and SDKs; over 1 million internet-exposed Boa server components in a week; Realtek SDK updates do not include patches for Boa vulnerabilities; Boa affected by known vulnerabilities including CVE-2009-4496. — Microsoft Security blog
- CVE-2009-4496 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.12403, percentile 0.96277, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Is there a fixed Boa version for CVE-2009-4496?
No. NVD lists Boa 0.94.14rc21, the Boa home page was last updated in February 2005, and the 2010 ush.it advisory records no vendor response. Any fix is a patch the device maker carries in its own Boa copy (per NVD, the Boa home page and the ush.it advisory).
Who is at risk from CVE-2009-4496 on an embedded device?
The person who reads the Boa log in a terminal, for example over a serial console or SSH during support. The request itself only writes the escape sequence to the log; it acts when the log is printed with a tool such as cat or tail (per the ush.it advisory and NVD).
Why does Microsoft's Boa report cite CVE-2009-4496?
Microsoft Threat Intelligence names it among Boa's known vulnerabilities in its November 2022 report on Boa in IoT SDKs, and says Realtek SDK updates do not include patches for Boa itself (per Microsoft Threat Intelligence).
Is CVE-2009-4496 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.12403, the 96th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?