CVE-2012-1747
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 Network Layer component in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, and 11.2.0.3, when running on Windows, allows remote attackers to affect availability via unknown vectors, a different vulnerability than CVE-2012-1746.
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 confidenceVulnerability in the Oracle Database Server Network Layer component affecting Windows platforms (versions 10.2.0.3-10.2.0.5, 11.1.0.7, 11.2.0.2, and 11.2.0.3). Allows remote attackers to impact availability through unspecified vectors in the network layer, enabling potential denial of service.
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.2.0.3= 10.2.0.4= 10.2.0.5= 11.1.0.7= 11.2.0.2= 11.2.0.3CVSS 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.
-
Verify Windows platformRun 'systeminfo | findstr /B /C:"OS Name"' or check OS via 'winver' or System Properties. Confirm the Oracle Database server is running on a Windows host.Affected if The Oracle Database instance is running on a non-Windows platform, then this CVE does not apply.
-
Identify Oracle Database versionConnect to the database as SYSDBA and run 'SELECT * FROM V$VERSION;' or check the Oracle inventory via 'ORACLE_HOME/Inventory/ContentsXML'. Alternatively, run 'sqlplus -v' from the Oracle home bin directory.Affected if The installed version is exactly 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, or 11.2.0.3.
-
Confirm Oracle TNS Listener is activeRun 'lsnrctl status' from the Oracle bin directory, or check for the TNSLSNR.exe process in Task Manager on Windows services.Affected if The TNS Listener service is not running, the network layer vector may not be exploitable, though the vulnerable code may still be present.
-
Check network exposure of Oracle listenerRun 'lsnrctl status' and review the 'Host' and 'Port' entries. Use 'netstat -an | findstr 1521' (or your configured port) to check listening addresses. Verify if the listener is bound to 0.0.0.0 or a public IP versus localhost/127.0.0.1.Affected if The listener is exposed to untrusted networks (0.0.0.0 or public IP), increasing the risk of remote exploitation.
You are affected if your Oracle Database runs on Windows AND the installed version matches one of 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, or 11.2.0.3 AND the TNS Listener is active and network-accessible.
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 the Oracle Critical Patch Update (CPU) for July 2012 that addresses CVE-2012-1747. Since this only affects Windows deployments, prioritize patching Windows-based Oracle Database instances. If immediate patching is not feasible, consider network segmentation to limit exposure of the Oracle listener to untrusted networks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1747 — 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-1747 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