CVE-2007-2112
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 Authentication component for Oracle Database 10.1.0.5 and 10.2.0.3 has unknown impact and attack vectors, aka DB05. NOTE: as of 20070424, Oracle has not disputed reliable claims that this issue allows remote authenticated users to bypass the AUTH_ALTER_SESSION security policies via a logon trigger ("AFTER LOGON ON DATABASE" trigger directive), a related issue to CVE-2006-0547.
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 confidenceOracle Database 10.1.0.5 and 10.2.0.3 Authentication component vulnerability allowing remote authenticated users to bypass AUTH_ALTER_SESSION security policies via logon triggers ('AFTER LOGON ON DATABASE' trigger directive). Related to CVE-2006-0547.
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= 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 Database versionExecute SELECT banner FROM v$version WHERE banner LIKE 'Oracle%'; or SELECT version FROM product_component_version WHERE product LIKE 'Oracle Database%';Affected if Version equals 10.1.0.5 or 10.2.0.3 exactly
-
Check for existing logon triggersQuery SELECT trigger_name, trigger_type, table_name FROM user_triggers WHERE trigger_type LIKE '%LOGON%'; or SELECT owner, trigger_name, trigger_type FROM dba_triggers WHERE trigger_type LIKE '%LOGON%';Affected if Any triggers with LOGON in the trigger_type column exist in the database
-
Identify AFTER LOGON ON DATABASE triggersExamine the trigger definition by querying SELECT trigger_name, trigger_body FROM user_triggers WHERE trigger_type = 'AFTER LOGON' AND table_name IS NULL; or check DBA_TRIGGERS for schema-level logon triggersAffected if Triggers with type 'AFTER LOGON' operating at the DATABASE level (schema-level, not schema-specific) are defined
-
Verify AUTH_ALTER_SESSION security policiesQuery SELECT policy_name, package_name FROM dba_policies WHERE policy_name = 'AUTH_ALTER_SESSION'; or check if any policies with AUTH_ALTER_SESSION exist in DBA_POLICIESAffected if AUTH_ALTER_SESSION security policies are present and intended to restrict ALTER SESSION privileges
A user is affected if running Oracle Database exactly version 10.1.0.5 or 10.2.0.3 AND has AFTER LOGON ON DATABASE triggers defined, which can bypass AUTH_ALTER_SESSION security policies for authenticated users.
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 Update for April 2007 or later; review and restrict unnecessary logon triggers that may bypass authentication security policies.
- 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-2112 — 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-2112 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