CVE-2012-3221: Low severity oracle virtualization vulnerability

Published Oct 17, 2012
·
Updated

Unspecified vulnerability in the Oracle VM Virtual Box component in Oracle Virtualization 3.2, 4.0, and 4.1 allows local users to affect availability via unknown vectors related to VirtualBox Core. NOTE: The previous information was obtained from the October 2012 CPU. Oracle has not commented on claims from another vendor that this issue is related to "incorrect interrupt handling."

Affected Software

3 affected components
Oracle Virtualization=3.2
Oracle Virtualization=4.0
Oracle Virtualization=4.1

Event History

Oct 17, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-3221?

CVE-2012-3221 is classified as a vulnerability that can potentially affect the availability of the Oracle VM Virtual Box.

2

How do I fix CVE-2012-3221?

To fix CVE-2012-3221, you should update your Oracle Virtualization software to the latest available version that addresses this vulnerability.

3

What versions of Oracle Virtualization are affected by CVE-2012-3221?

CVE-2012-3221 affects Oracle Virtualization versions 3.2, 4.0, and 4.1.

4

Who should be concerned about CVE-2012-3221?

Local users of the affected versions of Oracle VM Virtual Box should be concerned about CVE-2012-3221 due to potential impact on system availability.

5

Is there a public exploit for CVE-2012-3221?

As of now, there has been no public exploit released for CVE-2012-3221, but the vulnerability itself poses a risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203