CVE-2009-3566 json
McAfee IntruShield Network Security Manager (NSM) before 5.1.11.8.1 does not include the HTTPOnly flag in the Set-Cookie header for the ses…
published 2009-11-13 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3547
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
McAfee IntruShield Network Security Manager (NSM) before 5.1.11.8.1 does not include the HTTPOnly flag in the Set-Cookie header for the session identifier, which allows remote attackers to hijack a session by leveraging a cross-site scripting (XSS) vulnerability.
Timeline
- First public exploit (EDB-33347)
- Published
Exploit prediction
4.04% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-33347 McAfee Network Security Manager 5.1.7 - Information Disclosure webapps, 2009-11-06
- securityfocus.com http://www.securityfocus.com/bid/37004 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
securityfocus.com
/bid/37004
vdb-entry, exploit
-
kc.mcafee.com
/corporate/index?page=content&id=SB10005
vendor-advisory
-
vupen.com
/english/advisories/2009/3226
vdb-entry, vendor-advisory
-
secunia.com
/advisories/37178
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1023172
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54251
vdb-entry
-
osvdb.org
/59912
vdb-entry
-
securityfocus.com
/archive/1/507822/100/0/threaded
mailing-list
- secureworks.com /ctu/advisories/SWRX-2009-002
Sources
- CVE List CVE-2009-3566
- NVD CVE-2009-3566
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.