CVE-2007-5507
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 GIOP service in TNS Listener in the Oracle Net Services 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 (crash) or read potentially sensitive memory via a connect GIOP packet with an invalid data size, which triggers a buffer over-read, aka DB22.
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 confidenceBuffer over-read vulnerability in the GIOP service within Oracle TNS Listener. Remote attackers can send a malformed connect GIOP packet with an invalid data size, triggering the over-read. This causes denial of service (listener crash) or potentially allows reading sensitive memory contents.
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
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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 Server versionConnect to the database using SQL*Plus and run: SELECT VERSION FROM V$INSTANCE; or check the Oracle inventory files in $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml, or inspect the oratab file typically located in /etc/oratab or /etc/oratabAffected if The reported version matches any of these: 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
-
Verify TNS Listener is runningRun command: ps -ef | grep tnslsnr to check if the Oracle TNS Listener process is active, or use lsnrctl status to query the listener's current stateAffected if The TNS Listener process (tnslsnr) is running and accepting connections on the network
-
Confirm network exposure of TNS Listener portRun: netstat -an | grep 1521 or ss -tlnp | grep 1521 to see if the default TNS port (1521) is listening on network interfaces. Check firewall rules with iptables -L or equivalent for inbound rules on port 1521Affected if Port 1521 is bound to a network interface accessible from untrusted networks (0.0.0.0 or public IP rather than localhost/127.0.0.1 only)
-
Check for GIOP protocol support in TNS ListenerReview the listener.ora configuration file typically found in $ORACLE_HOME/network/admin/listener.ora and look for GIOP-related parameters or protocol_adapters, or use lsnrctl services to list all registered services and protocolsAffected if GIOP (General Inter-ORB Protocol) support is enabled in the TNS Listener configuration, which is required for the vulnerable code path to be reachable
Your environment is affected if you run any of the specific versions listed (9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, 10.2.0.3), have TNS Listener running with GIOP support exposed to the network.
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 for the affected versions (9.x, 10.1.x, 10.2.x). Additionally, restrict network access to the TNS Listener port (typically 1521) using firewall rules or Oracle Advanced Security options to limit exposure to untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5507 — 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-5507 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