CVE-2012-2561
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 · uneditedHP Business Service Management (BSM) 9.12 does not properly restrict the uploading of .war files, which allows remote attackers to execute arbitrary JSP code within the JBOSS Application Server component via a crafted request to TCP port 1098, 1099, or 4444.
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 confidenceHP Business Service Management 9.12 fails to validate or restrict .war file uploads to its JBOSS Application Server component, allowing remote attackers to deploy malicious web archives containing arbitrary JSP code. The vulnerability is exploitable via crafted HTTP requests to JBOSS-related TCP ports 1098, 1099, or 4444, leading to complete remote code execution on the affected system.
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= 9.12CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 HP Business Service Management versionCheck the installed version of HP Business Service Management in the system inventory, registry, or product installation directory. Look for version 9.12 specifically.Affected if The installed version is exactly 9.12
-
Confirm JBOSS component is activeCheck if the JBOSS Application Server component is running as part of HP Business Service Management. Look for JBOSS processes in task manager or running services.Affected if JBOSS is running as part of the HP BSM installation
-
Detect open JBOSS portsRun a network port scan or use netstat to check if TCP ports 1098, 1099, or 4444 are listening on the system.Affected if Any of ports 1098, 1099, or 4444 are open and accessible
-
Check network accessibility of JBOSS portsVerify whether these JBOSS ports are bound to 0.0.0.0 (all interfaces) or are exposed to untrusted networks, rather than localhost only.Affected if Ports 1098/1099/4444 are bound to all interfaces or accessible from untrusted networks
The environment is affected if HP Business Service Management version 9.12 is installed with JBOSS enabled and ports 1098/1099/4444 are exposed on the network.
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 patch for CVE-2012-2561 if available, or restrict network access to ports 1098/1099/4444 and implement strict file-type validation for upload functionalities. If JBOSS is not required for business operations, consider disabling the component.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2561 — 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-2561 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