CVE-2006-2316 json
S24EvMon.exe in the Intel PROset/Wireless software, possibly 10.1.0.33, uses a S24EventManagerSharedMemory shared memory section with weak…
published 2006-05-12 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2317
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 1
- Exploit-DB
Summary
S24EvMon.exe in the Intel PROset/Wireless software, possibly 10.1.0.33, uses a S24EventManagerSharedMemory shared memory section with weak permissions, which allows local users to read or modify passwords or other data, or cause a denial of service.
Timeline
- First public exploit (EDB-1772)
- Published
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-1772 Intel Wireless Service - 's24evmon.exe' Shared Memory local, 2006-05-09
- reversemode.com http://www.reversemode.com/index.php?option=com_content&task=view&id=10&Itemid=1 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/17914 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:C/I:N/A:N |
References
-
reversemode.com
/index.php?option=com_content&task=view&id=10&Itemid=1
exploit
-
securityfocus.com
/bid/17914
vdb-entry, exploit
-
secunia.com
/advisories/20001
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26317
vdb-entry
-
securityfocus.com
/archive/1/433133/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/877
third-party-advisory
-
securitytracker.com
/id?1016621
vdb-entry
-
vupen.com
/english/advisories/2006/1737
vdb-entry
Sources
- CVE List CVE-2006-2316
- NVD CVE-2006-2316
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.