dbcve.org
Tivoli Provisioning Manager Express For Software DistributionApplication · Ibm

CVE-2012-0199

HIGH · 7.5 CVSS v2.0 Published 2012-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Multiple SQL injection vulnerabilities in IBM Tivoli Provisioning Manager Express for Software Distribution 4.1.1 allow remote attackers to execute arbitrary SQL commands via (1) a SOAP message to the Printer.getPrinterAgentKey function in the SoapServlet servlet, (2) the User.updateUserValue function in the register.do servlet, (3) the User.isExistingUser function in the logon.do servlet, (4) the Asset.getHWKey function in the CallHomeExec servlet, (5) the Asset.getMimeType function in the getAttachment (aka GetAttachmentServlet) servlet, (6) the addAsset.do servlet, or (7) a crafted EG2 file.

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 confidence

Multiple SQL injection vulnerabilities in IBM Tivoli Provisioning Manager Express for Software Distribution 4.1.1 allow remote attackers to execute arbitrary SQL commands via seven different attack vectors including SOAP messages (Printer.getPrinterAgentKey), servlet parameters (User.updateUserValue, User.isExistingUser, Asset.getHWKey, Asset.getMimeType), and file uploads (EG2 files). The vulnerabilities exist across SoapServlet, register.do, logon.do, CallHomeExec, GetAttachmentServlet, and addAsset.do.

MitigationImplement parameterized queries or prepared statements for all database interactions in the affected servlets and functions. Apply input validation on all user-supplied parameters before using them in SQL queries. Consider deploying a WAF as an interim control.

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
Tivoli Provisioning Manager Express For Software DistributionApplication
Affected:= 4.1.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm product version
    Check the installed version of IBM Tivoli Provisioning Manager Express for Software Distribution. This can typically be found in the product's about page, version.info file, or by querying the installed packages. Common locations include the installation directory or system inventory.
    Affected if The installed version is exactly 4.1.1 (only this specific version is affected)
  2. Verify SoapServlet exposure
    Check if the SoapServlet endpoint is accessible. This is typically exposed at a path like /soap/servlet or /servlet/soap. Attempt a simple HTTP request to these paths to confirm the service is running.
    Affected if The SoapServlet is exposed and responds to requests - this is one of the seven attack vectors for SQL injection
  3. Identify accessible servlets
    Probe for the affected servlet endpoints: /register.do, /logon.do, /addAsset.do. These servlets handle user registration, authentication, and asset management functions.
    Affected if Any of these servlets are accessible and accept user-supplied parameters without proper sanitization
  4. Check file upload capability
    Identify if the system accepts file uploads, particularly EG2 files. Look for upload functionality in the web interface or API endpoints that accept file attachments.
    Affected if File upload functionality exists and accepts EG2 file attachments - this is another attack vector
  5. Review access logs for SQL injection patterns
    Examine HTTP access logs and application logs for suspicious query patterns targeting the affected endpoints. Look for SQL meta-characters like quotes, UNION, SELECT, or common SQL injection payloads in request parameters.
    Affected if Logs show attempts to inject SQL syntax into parameters of the affected servlets or file upload fields

A user is affected if they are running exactly version 4.1.1 AND have any of the vulnerable components (SoapServlet, register.do, logon.do, addAsset.do, CallHomeExec, GetAttachmentServlet) exposed and accessible to network users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database interactions in the affected servlets and functions. Apply input validation on all user-supplied parameters before using them in SQL queries. Consider deploying a WAF as an interim control.

Fix this in Tivoli Provisioning Manager Express For Software Distribution Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0199 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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