CVE-2007-5506
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 · uneditedThe Core RDBMS component in Oracle Database 9.0.1.5+, 9.2.0.8, 9.2.0.8DV, 10.1.0.5, and 10.2.0.3 allows remote attackers to cause a denial of service (CPU consumption) via a crafted type 6 Data packet, aka DB20.
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 confidenceThis is a denial of service vulnerability in Oracle Database's Core RDBMS component. Remote unauthenticated attackers can cause excessive CPU consumption by sending a specially crafted type 6 Data packet to the Oracle database server, potentially rendering the database unresponsive.
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= 9.0.1.5= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 installationCheck for Oracle database binaries or running Oracle processes on the system. Look for Oracle-related processes (like ora_pmon_<sid>) or check installed Oracle software directories.Affected if Oracle Database Server software is installed on the system
-
Determine Oracle Database versionConnect to the database using SQL*Plus or SQL and run: SELECT * FROM v$version; or check the oratab/oraInventory for installed version information.Affected if The installed version matches one of the affected versions: 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
-
Verify network accessibilityCheck if the Oracle TNS Listener is running and exposed to the network. Use commands like 'lsnrctl status' or scan for open ports (typically 1521). Verify the listener configuration in listener.ora.Affected if The database listener is accessible from untrusted networks, allowing remote unauthenticated connections
-
Confirm type 6 packet exposureReview network segmentation and firewall rules around the database server. Verify that access to the Oracle TNS port (default 1521) is not restricted to authorized hosts only.Affected if Type 6 Data packets can reach the Oracle database from unauthenticated remote sources
You are affected if your environment runs Oracle Database Server version 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3 and the database is accessible over the network to unauthenticated attackers.
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 relevant Oracle Critical Patch Update (CPU) for this vulnerability (Oct 2007) or upgrade to a patched Oracle Database version. Consider network-level filtering to restrict unauthorized access to database ports.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.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 $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5506 — 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-5506 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