CVE-2007-5897
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 · uneditedBuffer overflow in MDSYS.SDO_CS in Oracle Database Server 8iR3, 9iR1, 9iR2 up to 9.2.0.6, and 10gR1 up to 10.1.0.4 allows remote authenticated users to cause a denial of service (crash) and execute arbitrary code via the TRANSFORM function. NOTE: this issue might already be covered by CVE-2007-5515, CVE-2007-5509, or CVE-2007-5505, but there are insufficient details to be sure.
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 · high confidenceBuffer overflow vulnerability in MDSYS.SDO_CS (Oracle Spatial coordinate transformation) allows authenticated remote database users to crash the service or execute arbitrary code via the TRANSFORM function.
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 dataall versions= 9.2.0.1= 9.2.0.2= 9.2.0.3= 9.2.0.4= 9.2.0.5= 9.2.0.6= 10.1.0.2= 10.1.0.3= 10.1.0.4CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/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 versionConnect to the database as a privileged user (e.g., SYS or SYSTEM) and run: SELECT * FROM v$version; or SELECT version FROM product_component_version WHERE product LIKE 'Oracle Database%';Affected if The version falls within 9.2.0.1-9.2.0.6, 10.1.0.2-10.1.0.4, or is an unspecified 'all versions' release that has not been patched.
-
Confirm Oracle Spatial (MDSYS) is installedRun: SELECT owner, object_name FROM dba_objects WHERE object_name = 'SDO_CS' AND object_type = 'PACKAGE';Affected if The MDSYS.SDO_CS package exists in the database, indicating Oracle Spatial component is present.
-
Verify user access to SDO_CS.TRANSFORM functionCheck privileges by querying: SELECT grantee, privilege FROM dba_tab_privs WHERE table_name = 'SDO_CS'; or attempt to execute: SELECT MDSYS.SDO_CS.TRANSFORM(...) FROM dual; as a test user.Affected if Authenticated database users (including low-privilege users) can execute or have granted EXECUTE privilege on the MDSYS.SDO_CS package.
-
Confirm Oracle Spatial is enabledRun: SELECT param, value FROM mdsys.srs$ where param = 'DIMINFO'; or check if MDSYS user schema objects are valid by querying: SELECT status, count(*) FROM dba_objects WHERE owner = 'MDSYS' GROUP BY status;Affected if Oracle Spatial component is valid and loaded in the database.
If your Oracle Database version is 9.2.0.1-9.2.0.6, 10.1.0.2-10.1.0.4 (or any unpatched version), Oracle Spatial (MDSYS) is installed, and authenticated users can access the SDO_CS.TRANSFORM function, then your environment is affected by this vulnerability.
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 addressing this vulnerability; for legacy systems on 8i/9i/10gR1, consider upgrading to supported Oracle versions as patches may no longer be available.
- 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-5897 — 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-5897 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