CVE-2012-1745
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 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 · low confidenceVulnerability in the Oracle Database Network Layer component affecting versions 10.2.0.3 through 11.2.0.3. Allows remote attackers to impact system availability through unspecified vectors in the network layer.
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.
-
Identify Oracle Database versionConnect to the database using SQL*Plus and execute: SELECT VERSION FROM V$INSTANCE; Alternatively, check the Oracle Inventory or opatch lsinventory output for the exact version stringAffected if The version shown matches 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 Network Layer component exposureCheck if the TNS Listener service is running and listening on network ports (default 1521). Use command: lsnrctl status LISTENER or netstat -an | grep 1521 to verify the listener is accessible over the networkAffected if The TNS Listener is exposed to network and the database version falls within the affected range
-
Verify applied Oracle patchesRun opatch lsinventory on the database host to list installed patches. Look for CPU patches from April 2012 or later (e.g., patches 13923374, 13923375, or subsequent patch numbers)Affected if No Oracle Critical Patch Update patches from April 2012 or later are installed and the database version is in the affected list
The environment is affected if the Oracle Database version is one of the listed affected versions (10.2.0.3 through 11.2.0.3) AND the TNS Listener is network-accessible AND no corresponding CPU patches from April 2012 or later have been applied.
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 April 2012 or later. Implement network segmentation and access controls as interim measures while planning patch deployment.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1745 — 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-1745 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