CVE-2007-2123
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 Portal component in Oracle Application Server 10.1.3 up to 10.1.3.2.0, 10.1.2 up to 10.1.2.2.0, and 9.0.4.3 has unknown impact and attack vectors, aka AS04.
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 Oracle Application Server Portal component affecting versions 9.0.4.3, 10.1.2.x through 10.1.2.2.0, and 10.1.3.x through 10.1.3.2.0. The exact vulnerability type and attack vector are not disclosed in the vulnerability note; CVSS 10 indicates potential for complete system compromise (likely remote code execution or authentication bypass). This was part of Oracle's April 2007 Critical Patch Update.
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.4.3= 10.1.2.0.0= 10.1.2.0.2= 10.1.2.2= 10.1.3.0= 10.1.3.2.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/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 Application Server installationLocate Oracle Application Server binary directories or check for Oracle inventory entries. Common locations include $ORACLE_HOME and /etc/oraInst.loc on Unix or registry entries on Windows.Affected if Oracle Application Server is installed and the Portal component is present
-
Determine Oracle Application Server versionRun 'opatch lsinventory' or check the version string in $ORACLE_HOME/oraInst.loc, or query the Oracle Inventory using 'lsinventory' command. The version will appear in format like 9.0.4.3, 10.1.2.0.0, 10.1.2.2, 10.1.3.0, or 10.1.3.2.0.Affected if The installed version matches exactly 9.0.4.3, 10.1.2.0.0, 10.1.2.0.2, 10.1.2.2, 10.1.3.0, or 10.1.3.2.0
-
Verify Portal component is configuredCheck if the OracleAS Portal is configured by examining the ORACLE_HOME/portal directory or by querying the Oracle Application Server deployment status. The Portal typically runs on port 7777 or 7778 by default.Affected if The Portal component is installed and configured on the affected version
-
Confirm Portal is accessible and runningAttempt to access the Portal URL (typically http://hostname:7777/pls/portal or similar) or check running processes for portal-related Java processes.Affected if The Portal service is active and responding
The system is affected if Oracle Application Server is installed with version 9.0.4.3, 10.1.2.0.0, 10.1.2.0.2, 10.1.2.2, 10.1.3.0, or 10.1.3.2.0 AND the Portal component is configured and running.
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 April 2007 (or subsequent relevant patches). Given the age of these Oracle Application Server versions (circa 2007), strongly consider upgrading to a supported Oracle Fusion Middleware version or migrating to a supported platform, as older versions are likely end-of-life and may have additional unpatched vulnerabilities.
- 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-2123 — 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-2123 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