CVE-2007-2134
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 HTML Server in Oracle JD Edwards EnterpriseOne SP23_Q1 and 8.96.I1 has unknown impact and local attack vectors, aka JDE01.
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 · low confidenceVulnerability in Oracle JD Edwards EnterpriseOne HTML Server (versions SP23_Q1 and 8.96.I1) with unspecified nature and local attack vectors. The exact vulnerability type and impact are not disclosed in available sources.
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= 8.96.11= sp23_q1CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 installed EnterpriseOne versionQuery the EnterpriseOne deployment or check installation metadata for the exact version release (such as SP23_Q1 or 8.96.I1). This may be found in installation logs, deployment configuration files, or version control systems used for the EnterpriseOne implementation.Affected if The installed version is exactly SP23_Q1 or 8.96.I1 (8.96.11)
-
Verify HTML Server component is deployedLocate and inspect the Oracle JD Edwards EnterpriseOne HTML Server installation directory or configuration. Check for the presence of HTML Server binaries, configuration files, or services associated with the EnterpriseOne web tier.Affected if HTML Server component is installed and active in the environment
-
Confirm local accessibility to the systemReview system access controls and determine whether untrusted local users or processes could interact with the HTML Server. Check for multi-user environments, shared systems, or terminals where local access is possible.Affected if The system allows local user access or hosts untrusted local accounts
-
Check for legacy patch statusExamine patch inventory or release documentation to determine whether the April 2007 Critical Patch Update or any subsequent updates have been applied to the EnterpriseOne installation.Affected if No patches from April 2007 or later have been applied to this installation
The environment is affected if EnterpriseOne version SP23_Q1 or 8.96.I1 is installed with the HTML Server component and has not received the April 2007 or later Oracle Critical Patch Update.
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, as this is a legacy vulnerability from 2007 affecting very old EnterpriseOne versions that may have reached end-of-life.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2134 — 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-2134 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