CVE-2013-0420 json
Unspecified vulnerability in the VirtualBox component in Oracle Virtualization 4.0, 4.1, and 4.2 allows local users to affect integrity and…
published 13y ago modified 4mo ago also EUVD-2013-0431
- cvss
- 2.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the VirtualBox component in Oracle Virtualization 4.0, 4.1, and 4.2 allows local users to affect integrity and availability via unknown vectors related to Core. NOTE: The previous information was obtained from the January 2013 Oracle CPU. Oracle has not commented on claims from another vendor that this issue is related to an incorrect comparison in the vga_draw_text function in Devices/Graphics/DevVGA.cpp, which can cause VirtualBox to "draw more lines than necessary."
Patch / fix
Is CVE-2013-0420 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- virtualbox.org https://www.virtualbox.org/changeset/44055/vbox referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.4 | AV:L/AC:H/Au:S/C:N/I:P/A:P |
References
-
virtualbox.org
/changeset/44055/vbox
exploit, patch
-
bugzilla.novell.com
/show_bug.cgi?id=798776
patch
-
lists.opensuse.org
/opensuse-updates/2013-02/msg00000.html
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2013:150
vendor-advisory
-
oracle.com
/technetwork/topics/security/cpujan2013-1515902.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15763
vdb-entry, signature
Sources
- CVE List CVE-2013-0420
- NVD CVE-2013-0420
Fencer Intel 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.