CVE-2012-0072
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnspecified vulnerability in the Listener component in Oracle Database Server 10.1.0.5, 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, and 11.2.0.2 allows remote attackers to affect availability via unknown vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn unspecified vulnerability in the Oracle TNS Listener component allows remote attackers to impact availability through unknown vectors. The vulnerability affects multiple versions of Oracle Database Server (10.1.0.5 through 11.2.0.2) and is exploitable remotely without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.1.0.5= 10.2.0.3= 10.2.0.4= 10.2.0.5= 11.1.0.7= 11.2.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Oracle TNS Listener is runningRun 'lsnrctl status' or 'lsnrctl version' on the database server to see if the TNS Listener process is active. Alternatively, check for processes named 'tnslsnr' or check if port 1521 (default Oracle listener port) is open on the system.Affected if The TNS Listener process is running and listening on a network port, making it potentially reachable.
-
Determine the Oracle Database versionExecute 'lsnrctl version' to retrieve the TNS Listener version, or connect to the database and run 'SELECT * FROM V$VERSION;' to get the exact database server version number.Affected if The installed version matches any of these: 10.1.0.5, 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, or 11.2.0.2.
-
Verify network accessibility of TNS ListenerUse 'netstat -an | grep 1521' or a port scanner to confirm port 1521 (or custom listener port) is bound to a network interface other than localhost (0.0.0.0 or actual IP). Check the listener.ora file for the ADDRESS configuration.Affected if The TNS Listener is bound to a non-localhost address or is accessible from network segments beyond the local host.
-
Check listener.ora configuration for security settingsLocate the listener.ora file (typically in $ORACLE_HOME/network/admin/) and review the listener configuration for ADMIN_RESTRICTIONS, SECURE_REGISTER, or encryption settings.Affected if The listener lacks encryption, authentication, or admin restrictions and accepts remote connections without additional security controls.
If the TNS Listener is running a version among 10.1.0.5, 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, or 11.2.0.2 and is network-accessible, the environment is potentially affected by CVE-2012-0072.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Oracle Critical Patch Update (CPU) patches for the affected versions. Restrict network access to the Oracle Listener using firewall rules and ensure Listener encryption/authentication are enabled. Implement Oracle's recommended security configurations for the TNS Listener.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data