CVE-2007-5520
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 Oracle Internet Directory component in Oracle Database 9.2.0.8 and 9.2.0.8DV, and Oracle Application Server 9.0.4.3, 10.1.3.0.0 up to 10.1.3.3.0, and 10.1.2.0.1 up to 10.1.2.2.0, has unknown impact and remote attack vectors, aka AS05.
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 confidenceUnspecified vulnerability in Oracle Internet Directory (OID) affecting Oracle Database 9.2.0.8, 9.2.0.8DV, and Oracle Application Server versions 9.0.4.3, 10.1.3.0.0-10.1.3.3.0, and 10.1.2.0.1-10.1.2.2.0. The CVSS score of 7.5 indicates remote network exploitation is possible with high impact to confidentiality and/or availability, though specific technical details remain undisclosed.
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.2.0.1= 10.1.2.0.2= 10.1.2.2= 10.1.3.0= 10.1.3.1= 10.1.3.2.0= 10.1.3.3= 9.2.0.8= 9.2.0.8dvCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 if Oracle Internet Directory component is installedQuery the Oracle Inventory or use opatch lsinventory to list installed components. On Unix systems check $ORACLE_HOME/oracore/zoneinfo or look for oidldapd processes. On Windows check services for Oracle Internet Directory.Affected if Oracle Internet Directory (OID) is present in the environment
-
Determine Oracle Database version if OID is part of database installationConnect to the database as SYSDBA and run: SELECT VERSION FROM V$INSTANCE; or check the $ORACLE_HOME/oraInst.loc inventory file for version details.Affected if Version is 9.2.0.8 or 9.2.0.8DV
-
Determine Oracle Application Server version if OID is part of AS installationCheck the central inventory $ORACLE_HOME/oraInst.loc, or look at the Oracle Application Server version file in $ORACLE_HOME/Apache/Apache/version or run iasversion. Alternatively check opatch lsinventory for AS components.Affected if Version matches 10.1.2.0.1, 10.1.2.0.2, 10.1.2.2, 10.1.3.0, 10.1.3.1, 10.1.3.2.0, or 10.1.3.3, or is 9.0.4.3
-
Confirm OID component is actually in use or runningCheck for running oidldapd or oidmon processes using ps (Unix) or Task Manager (Windows). Also verify port 389 or 636 (LDAP/LDAPS) is listening which indicates OID is active.Affected if Oracle Internet Directory processes are running and listening on LDAP ports
Environment is affected only if Oracle Internet Directory is installed AND the underlying Oracle Database or Application Server version matches the specific versions listed (9.2.0.8, 9.2.0.8DV, or the listed AS versions).
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 Updates (CPUs) from October 2007 or later that address AS05. For legacy systems no longer under Oracle support, consider network isolation, upgrading to supported versions, or decommissioning if feasible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5520 — 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-2007-5520 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