CVE-2009-1967
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 Config Management component in (1) Oracle Database 11.1.0.7 and (2) Oracle Enterprise Manager 10.2.0.4 allows remote authenticated users to affect confidentiality and integrity via unknown vectors, a different vulnerability than CVE-2009-1966.
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 the Config Management component of Oracle Database 11.1.0.7 and Oracle Enterprise Manager 10.2.0.4 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to configuration settings.
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= 11.1.0.7= 10.2.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
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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.
-
Check Oracle Database Server versionConnect to the database and run SELECT * FROM v$version; or check the Oracle inventory file ($ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml)Affected if The installed version is exactly 11.1.0.7
-
Check Oracle Enterprise Manager versionLog into the Enterprise Manager console and navigate to Help > About, or check the OMS ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml fileAffected if The installed version is exactly 10.2.0.4
-
Verify Config Management component is accessibleCheck if Oracle Configuration Manager (OCM) or the Config Management web interface is configured and reachable via the Oracle Enterprise Manager consoleAffected if The Config Management component is enabled and accessible to authenticated users
-
Assess network exposure of database and OEM interfacesReview listener.ora, sqlnet.ora, and Oracle Enterprise Manager console accessibility settings to determine if ports 1521 (listener), 1158/5500 (OEM), or 4889 (OMS) are exposed beyond trusted networksAffected if Database or Enterprise Manager interfaces are accessible to untrusted or anonymous network users
The environment is affected if either Oracle Database 11.1.0.7 or Oracle Enterprise Manager 10.2.0.4 is running with the Config Management component accessible to remote authenticated users over 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 (CPUs) from 2009 or later that address this vulnerability, or upgrade to supported versions; restrict network access to database and Enterprise Manager interfaces to trusted authenticated users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1967 — 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-2009-1967 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