CVE-2013-6321
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 · uneditedSQL injection vulnerability in IBM Atlas eDiscovery Process Management 6.0.1.5 and earlier and 6.0.2, Disposal and Governance Management for IT 6.0.1.5 and earlier and 6.0.2, and Global Retention Policy and Schedule Management 6.0.1.5 and earlier and 6.0.2 in IBM Atlas Suite (aka Atlas Policy Suite) allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in IBM Atlas Suite (Atlas Policy Suite) affecting multiple products including eDiscovery Process Management, Disposal and Governance Management for IT, and Global Retention Policy and Schedule Management. Allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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<= 6.0.1.5= 6.0.2all versions<= 6.0.1.5= 6.0.2<= 6.0.1.5= 6.0.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.
-
Identify installed IBM Atlas productsCheck system for installed IBM Atlas Suite components: look for installation directories (commonly under C:\Program Files\IBM\ or /opt/IBM/), check Windows Programs and Features, or use package management tools on Linux to list installed software containing 'Atlas' or 'eDiscovery'Affected if Any of these IBM Atlas products are installed: eDiscovery Process Management, Disposal and Governance Management for IT, Global Retention Policy and Schedule Management, or general Atlas Suite
-
Determine installed product versionCheck version information in the product installation directory, registry (Windows), or via product-specific about/version command. Common locations: installation_folder\version.ini, or look for version.txt in the product root directoryAffected if Version is 6.0.1.5 or earlier, equals 6.0.2, or for 'IBM Atlas Suite' any version (all versions affected)
-
Confirm web or API exposureIdentify if the Atlas web interface or REST API services are running and accessible. Check for web service processes (typically IBM WebSphere or similar), review firewall rules, and look for exposed HTTP/HTTPS ports (common defaults: 8080, 8443, 9080)Affected if The web interface or API is exposed to network users, making the SQL injection remotely exploitable
-
Review database query handlingInspect application logs, web server logs, and database audit logs for unusual or malformed SQL queries that may indicate exploitation attempts. Look for unsanitized input patterns in SQL statementsAffected if Evidence of SQL injection attempts or unsanitized user input reaching database queries is found
You are affected if any IBM Atlas product from the affected list is installed and the version falls within <=6.0.1.5, =6.0.2, or is any version of the general Atlas Suite, especially if the web interface is exposed.
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 IBM patches for the affected versions (6.0.1.5 and earlier, 6.0.2). If patches unavailable, audit and remediate database query handling using parameterized queries or stored procedures.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6321 — 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-2013-6321 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