CVE-2006-5330 json
CRLF injection vulnerability in Adobe Flash Player plugin 9.0.16 and earlier for Windows, 7.0.63 and earlier for Linux, 7.x before 7.0 r67…
published 2006-10-17 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5315
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 24.5%
- EPSS 24.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
CRLF injection vulnerability in Adobe Flash Player plugin 9.0.16 and earlier for Windows, 7.0.63 and earlier for Linux, 7.x before 7.0 r67 for Solaris, and before 9.0.28.0 for Mac OS X, allows remote attackers to modify HTTP headers of client requests and conduct HTTP Request Splitting attacks via CRLF sequences in arguments to the ActionScript functions (1) XML.addRequestHeader and (2) XML.contentType. NOTE: the flexibility of the attack varies depending on the type of web browser being used.
Patch / fix
- flash-plugin RHEL 3 EXTRAS 7.0.69-1.el3
- flash-plugin RHEL 4 EXTRAS 7.0.69-1.el4
red hat advisories RHSA-2007:0009
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-2006-5330 updated
security flaw
-
Red Hat Desktop version 3 Extras flash-plugin 7.0.69-1.el3 Red Hat Desktop version 4 Extras flash-plugin 7.0.69-1.el4 Red Hat Enterprise Linux AS version 3 Extras flash-plugin 7.0.69-1.el3 Red Hat Enterprise Linux AS version 4 Extras flash-plugin 7.0.69-1.el4 Red Hat Enterprise Linux ES version 3 Extras flash-plugin 7.0.69-1.el3 Red Hat Enterprise Linux ES version 4 Extras flash-plugin 7.0.69-1.el4fixed: vendor fix RHSA-2007:0009
+2 more productsfewer
Red Hat Enterprise Linux WS version 3 Extras flash-plugin 7.0.69-1.el3 Red Hat Enterprise Linux WS version 4 Extras flash-plugin 7.0.69-1.el4
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
Exploit prediction
24.47% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
sunsolve.sun.com
/search/document.do?assetkey=1-26-102932-1
vendor-advisory
-
lists.apple.com
/archives/security-announce/2007/Mar/msg00002.html
vendor-advisory
-
redhat.com
/support/errata/RHSA-2007-0009.html
vendor-advisory
-
lists.suse.com
/archive/suse-security-announce/2006-Dec/0006.html
vendor-advisory
-
secunia.com
/advisories/22467
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/23324
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/25467
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/23581
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/24479
third-party-advisory, vendor-advisory
- adobe.com /support/security/advisories/apsa06-01.html
-
us-cert.gov
/cas/techalerts/TA07-072A.html
third-party-advisory, us-government-resource
- docs.info.apple.com /article.html?artnum=305214
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29634
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11405
vdb-entry, signature
-
vupen.com
/english/advisories/2006/4094
vdb-entry
-
osvdb.org
/29863
vdb-entry
- adobe.com /support/security/bulletins/apsb06-18.html
- rapid7.com /advisories/R7-0026.jsp
-
securityfocus.com
/bid/20592
vdb-entry
-
vupen.com
/english/advisories/2007/0930
vdb-entry
-
securityreason.com
/securityalert/1737
third-party-advisory
-
vupen.com
/english/advisories/2007/1999
vdb-entry
-
securityfocus.com
/archive/1/448997/100/0/threaded
mailing-list
-
securitytracker.com
/id?1017078
vdb-entry
Sources
- CVE List CVE-2006-5330
- NVD CVE-2006-5330
Fencer Vulns 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.