CVE-2007-5521
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 Oracle Containers for J2EE component in Oracle Application Server 9.0.4.3, 10.1.2.0.2, 10.1.2.2, and 10.1.3.3, and Collaboration Suite 10.1.2, has unknown impact and remote attack vectors, aka AS06.
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 Containers for J2EE (OC4J) component of Oracle Application Server versions 9.0.4.3, 10.1.2.0.2, 10.1.2.2, and 10.1.3.3, and Collaboration Suite 10.1.2. The vulnerability has remote attack vectors with high severity (CVSS 7.5), but the exact nature of the flaw and its impact are not publicly disclosed.
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.2= 10.1.2.2= 10.1.3.3= 10.1.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.
-
Verify OC4J is installed and runningCheck for Oracle Containers for J2EE (OC4J) process or component. On UNIX/Linux: ps -ef | grep -i oc4j. On Windows: check services for OC4J or examine ORACLE_HOME directory for oc4j folders.Affected if OC4J is present and running on the system
-
Identify Oracle Application Server versionCheck the version of Oracle Application Server installation. Common locations: $ORACLE_HOME/oracore/bin/orasql or check inventory files. Execute: java -jar $ORACLE_HOME/oc4j/bin/oc4j.jar -version or examine opatch lsinventory output.Affected if Version equals 9.0.4.3, 10.1.2.0.2, 10.1.2.2, or 10.1.3.3
-
Identify Oracle Collaboration Suite versionCheck version of Oracle Collaboration Suite installation. Examine $ORACLE_HOME/oracore directory or run: cat $ORACLE_HOME/oraInst.loc or check registry/inventory files.Affected if Version equals 10.1.2
-
Confirm OC4J component is exposedVerify OC4J HTTP listener is accessible. Check configuration files: $ORACLE_HOME/j2ee/home/config/http-web-site.xml or default-web-site.xml for enabled OC4J ports (typically 8888, 8889, or 127.0.0.1:23791).Affected if OC4J HTTP port is open and accessible from network
System is affected if OC4J is running and the Oracle Application Server version equals 9.0.4.3, 10.1.2.0.2, 10.1.2.2, or 10.1.3.3, or Oracle Collaboration Suite version equals 10.1.2.
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 (CPU) patches for October 2007 or later that address CVE-2007-5521. For end-of-life versions no longer receiving patches, migrate to supported Oracle WebLogic Server or Oracle Fusion Middleware platforms.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5521 — 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-5521 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