CVE-2012-3336
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 · uneditedIBM InfoSphere Guardium 8.0, 8.01, and 8.2 is vulnerable to SQL injection. A remote authenticated attacker could send specially-crafted SQL statements to multiple scripts, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 78282.
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 · high confidenceIBM InfoSphere Guardium versions 8.0, 8.01, and 8.2 contains a SQL injection vulnerability in multiple scripts. A remote authenticated attacker can send specially-crafted SQL statements to exploit insufficient input sanitization, allowing the attacker to view, add, modify, or delete information in the back-end database.
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.0= 8.01= 8.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Guardium versionCheck the installed IBM InfoSphere Guardium version. This can typically be done via the Guardium web interface (System tab > General > Version) or by running the command 'guardium_version' or 'ls -la' in the Guardium installation directory.Affected if The installed version is 8.0, 8.01, or 8.2 exactly.
-
Identify accessible web scriptsReview the web application configuration to identify accessible JSP or servlet scripts that handle user input and interact with the back-end database. Check the web.xml deployment descriptor and the web application's directory structure.Affected if Scripts that accept user-supplied input and construct SQL queries without proper parameterization are exposed.
-
Confirm authentication is requiredVerify whether the Guardium web interface requires authentication for access. Test by attempting to access the vulnerable endpoints without credentials. Check the authentication configuration in the Guardium configuration files.Affected if The vulnerability is exploitable by a remote authenticated attacker, so confirm if authentication enforcement is present or if anonymous access is possible.
-
Review database user privilegesCheck the database configuration to determine what privileges the application database user has. Review the database connection configuration and the permissions assigned to the Guardium database account.Affected if The database user has elevated privileges (such as DDL or extensive DML permissions) that would allow an attacker to view, add, modify, or delete data if exploited.
A system is affected if it runs IBM InfoSphere Guardium version 8.0, 8.01, or 8.2 and has the vulnerable scripts accessible to authenticated 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 dataApply vendor-supplied patches or upgrade to a patched version of InfoSphere Guardium. As a compensating control, review and sanitize user inputs in affected scripts and implement parameterized queries where possible.
- 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-2012-3336 — 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-2012-3336 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