CVE-2009-0894 json
Heap-based buffer overflow in the decoder_create function in the initialization functionality in xvidcore/src/decoder.c in Xvid before 1.2.…
published 2009-06-02 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0891
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.7%
- EPSS 5.7% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Heap-based buffer overflow in the decoder_create function in the initialization functionality in xvidcore/src/decoder.c in Xvid before 1.2.2, as used by Windows Media Player and other applications, allows remote attackers to execute arbitrary code via vectors involving the DirectShow (aka DShow) frontend and improper handling of the XVID_ERR_MEMORY return code during processing of a crafted movie file. NOTE: some of these details are obtained from third party information.
Patch / fix
Exploit prediction
5.70% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- cvs.xvid.org http://cvs.xvid.org/cvs/viewvc.cgi/xvidcore/src/decoder.c referenced PoC, tagged "exploit" by a source, unverified
- cvs.xvid.org http://cvs.xvid.org/cvs/viewvc.cgi/xvidcore/src/decoder.c?r1=1.80&r2=1.81 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
cvs.xvid.org
/cvs/viewvc.cgi/xvidcore/src/decoder.c
exploit, patch
-
cvs.xvid.org
/cvs/viewvc.cgi/xvidcore/src/decoder.c?r1=1.80&r2=1.81
exploit, patch
-
securityfocus.com
/bid/35158
vdb-entry
- xvid.org /News.64.0.html?&cHash=0170b4e439&tx_ttnews%5BbackPid%5D=64&tx_ttnews%5Btt_news%5D=7
- it-isac.org /postings/cyber/alertdetail.php?id=4635&selyear=2009&menutype=menupublic
Sources
- CVE List CVE-2009-0894
- NVD CVE-2009-0894
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.