CVE-2006-1037
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 · uneditedSQL injection vulnerability in the Oracle Diagnostics module 2.2 and earlier allows remote attackers to execute arbitrary SQL commands via unknown attack 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 · moderate confidenceSQL injection vulnerability in Oracle Diagnostics module 2.2 and earlier allows remote attackers to execute arbitrary SQL commands. The specific attack vectors are not detailed in available documentation, and the vulnerability has a CVSS score of 7.5 (HIGH), indicating significant risk of confidentiality and integrity impact.
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= 2.0= 2.1= 2.2= 11.5.3= 11.5.4= 11.5.5= 11.5.6= 11.5.7= 11.5.8= 11.5.9= 11.5.10= 11.5.10.1= 11.5.10.2CVSS 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.
-
Identify Oracle Diagnostics module versionQuery the Oracle database for the diagnostics module version: SELECT version FROM all_modules WHERE module_name LIKE '%Diagnostics%'; or check the Oracle Application Manager for installed component versions.Affected if Version equals 2.0, 2.1, or 2.2 (any version 2.2 or earlier)
-
Identify Oracle E Business Suite versionQuery the database for the EBS version: SELECT release_name FROM fnd_product_groups; or check the About Oracle Applications page in the EBS responsibility menu.Affected if Version equals 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.5.10.1, or 11.5.10.2
-
Verify if Oracle Diagnostics module is enabledCheck the Oracle Applications Manager or system administrator responsibilities to confirm the Diagnostics module is loaded and accessible. Look for the Diagnostics responsibility in the user profile.Affected if The Diagnostics module is installed and enabled for any user or responsibility
-
Check network accessibility of the Diagnostics interfaceReview Oracle HTTP Server or Oracle Application Server configuration for URLs mapping to the Diagnostics module (typically under /OA_HTML or /diagnostics context). Verify firewall rules allowing external access to these paths.Affected if The Diagnostics module is exposed to network-accessible endpoints without authentication barriers
If Oracle Diagnostics module version 2.2 or earlier, OR Oracle E Business Suite versions 11.5.3 through 11.5.10.2 is installed with the Diagnostics module enabled and accessible, the environment is affected by this SQL injection 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 dataUpgrade from Oracle Diagnostics module 2.2 or earlier to a patched version; if upgrade is not feasible, implement input validation and parameterized queries in the module's database interactions, and restrict network access to the affected component.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1037 — 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-2006-1037 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