CVE-2015-0427 json
Unspecified vulnerability in the Oracle VM VirtualBox component in Oracle Virtualization VirtualBox prior to 4.3.20 allows local users to a…
published 11y ago modified 4mo ago also EUVD-2015-0440
- cvss
- 3.2
- 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 29%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Oracle VM VirtualBox component in Oracle Virtualization VirtualBox prior to 4.3.20 allows local users to affect integrity and availability via vectors related to VMSVGA virtual graphics device, a different vulnerability than CVE-2014-6588, CVE-2014-6589, CVE-2014-6590, and CVE-2014-6595.
Patch / fix
- virtualbox Ubuntu 14.04 LTS 4.3.10-dfsg-1ubuntu2
ubuntu advisories UBUNTU-CVE-2015-0427
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- virtualbox openSUSE Tumbleweed 5.1.10-2.5
opensuse advisories openSUSE-SU-2024:10020-1
Is CVE-2015-0427 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.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.2 | AV:L/AC:L/Au:S/C:N/I:P/A:P |
References
-
security.gentoo.org
/glsa/201612-27
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2015-02/msg00030.html
vendor-advisory
-
oracle.com
/technetwork/topics/security/cpujan2015-1972971.html
vendor-advisory
-
securityfocus.com
/bid/72216
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/100181
vdb-entry
Sources
- CVE List CVE-2015-0427
- NVD CVE-2015-0427
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.