CVE-2008-4835 in the critical feed json
SMB in the Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008 allow…
published 2009-01-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4814
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.9%
- EPSS 44.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
SMB in the Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008 allows remote attackers to execute arbitrary code via malformed values of unspecified "fields inside the SMB packets" in an NT Trans2 request, related to "insufficiently validating the buffer size," aka "SMB Validation Remote Code Execution Vulnerability."
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
44.92% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-001
vendor-advisory
- zerodayinitiative.com /advisories/ZDI-09-002/
-
vupen.com
/english/advisories/2009/0116
vdb-entry
-
us-cert.gov
/cas/techalerts/TA09-013A.html
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/33122
vdb-entry
-
securityfocus.com
/archive/1/500013/100/0/threaded
mailing-list
-
securitytracker.com
/id?1021560
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5248
vdb-entry, signature
Sources
- CVE List CVE-2008-4835
- NVD CVE-2008-4835
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.