CVE-2010-3600
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 Client System Analyzer component in Oracle Database Server 11.1.0.7 and 11.2.0.1 and Enterprise Manager Grid Control 10.2.0.5 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the January 2011 CPU. Oracle has not commented on claims from a reliable third party coordinator that this issue involves an exposed JSP script that accepts XML uploads in conjunction with NULL bytes in an unspecified parameter that allow execution of arbitrary code.
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 confidenceVulnerability in Oracle Database Client System Analyzer (versions 11.1.0.7, 11.2.0.1, and EM Grid Control 10.2.0.5) allows remote attackers full impact via unspecified vectors. Third-party reports indicate an exposed JSP script accepting XML uploads with NULL bytes enabling arbitrary code execution, though Oracle has not confirmed these technical details.
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= 11.2.0.1= 10.2.0.5CVSS 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.
-
Identify Oracle Database Server versionRun the following SQL query to determine the installed Oracle Database version: SELECT VERSION FROM V$INSTANCE;Affected if The version returned is exactly 11.1.0.7 or 11.2.0.1
-
Identify Oracle Enterprise Manager Grid Control versionCheck the EM Grid Control console version information or examine the installation directory for version metadata.Affected if The installed version is exactly 10.2.0.5
-
Locate Client System Analyzer componentSearch for the Client System Analyzer (CSA) component in the Oracle installation directories. On the database server, look for directories or files named 'csa' or 'ClientSystemAnalyzer' within the Oracle home structure.Affected if The Client System Analyzer component is present and installed on the system
-
Detect exposed JSP scripts accepting XML uploadsExamine the Oracle web application deployments for JSP pages related to XML upload functionality. Look in the EM Grid Control web directories or database HTTP/HTTPS listener configurations for scripts that handle XML file uploads.Affected if JSP scripts that accept XML uploads are exposed and accessible via HTTP/HTTPS endpoints
A system is affected if it runs Oracle Database Server version 11.1.0.7 or 11.2.0.1, or EM Grid Control version 10.2.0.5, and has the Client System Analyzer component enabled and accessible.
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) released January 2011 for affected versions; if patching is not feasible, disable or restrict access to the Client System Analyzer component.
- Consultation2.0 h
- Implementation4.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,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3600 — 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-2010-3600 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