CVE-2013-6331
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 Algo One, as used in MetaData Management Tools in UDS 4.7.0 through 5.0.0, ACSWeb in Algo Security Access Control Management 4.7.0 through 4.9.0, and ACSWeb in AlgoWebApps 5.0.0, allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, a different vulnerability than CVE-2013-6302.
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 Algo One affecting MetaData Management Tools (UDS 4.7.0-5.0.0), ACSWeb in Algo Security Access Control Management (4.7.0-4.9.0), and ACSWeb in AlgoWebApps 5.0.0. Allows remote authenticated users 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= 4.7.0= 4.7.1= 4.8.0= 4.9.0= 4.9.1= 5.0.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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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 IBM Algo One installationCheck for IBM Algo One processes running on the system, or look for installation directories commonly named 'IBM/AlgoOne' or similar. Query system services for Algo One related services.Affected if IBM Algo One software is found running on the system
-
Determine installed Algo One versionLocate version information in the installation directory, typically in a version file, About dialog, or check the product binaries for version metadata. Compare against affected versions 4.7.0 through 5.0.0.Affected if Installed version matches 4.7.0, 4.7.1, 4.8.0, 4.9.0, 4.9.1, or 5.0.0
-
Check if MetaData Management Tools (UDS) is configuredInspect the Algo One configuration for the MetaData Management Tools or UDS component. Look for UDS-related configuration files, services, or web endpoints in the installation.Affected if MetaData Management Tools (UDS) component is present and accessible
-
Check if ACSWeb is configuredInspect configuration for ACSWeb component under Algo Security Access Control Management or AlgoWebApps. Look for ACSWeb web application files, services, or accessible endpoints.Affected if ACSWeb component is present and accessible via web interface
-
Verify remote authentication is enabledCheck ACSWeb or UDS authentication configuration to determine if remote user authentication is enabled. Review user access controls and network exposure settings.Affected if Remote authentication is enabled and non-privileged users can access the affected components
Environment is affected if IBM Algo One versions 4.7.0-5.0.0 are installed with MetaData Management Tools (UDS) or ACSWeb components accessible to authenticated remote users.
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 dataUpgrade to a patched version beyond 5.0.0 when available. As an interim measure, implement strict least-privilege database accounts, enable WAF monitoring, and restrict ACSWeb/MetaData Management access to essential authenticated users only.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6331 — 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-6331 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