CVE-2015-0161
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 Security SiteProtector System 3.0 before 3.0.0.7, 3.1 before 3.1.0.4, and 3.1.1 before 3.1.1.2 allows remote authenticated users 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 Security SiteProtector System allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors. The flaw affects versions 3.0 before 3.0.0.7, 3.1 before 3.1.0.4, and 3.1.1 before 3.1.1.2.
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= 3.0= 3.0.0.1= 3.0.0.2= 3.0.0.3= 3.0.0.4= 3.0.0.5= 3.0.0.6= 3.1.0.0= 3.1.0.1= 3.1.0.2= 3.1.0.3= 3.1.1.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 the installed version of IBM Security SiteProtector SystemLocate the version information through the SiteProtector web interface (typically in the About or System Information section) or by checking the installation documentation for version file locations. Compare the found version against the affected ranges: 3.0.x before 3.0.0.7, 3.1.0.x before 3.1.0.4, or 3.1.1.x before 3.1.1.2.Affected if The installed version falls within 3.0 (all versions), 3.0.0.1 through 3.0.0.6, 3.1.0.0 through 3.1.0.3, or 3.1.1.0 through 3.1.1.1.
-
Confirm that remote authentication is required for the SiteProtector web interfaceVerify that the SiteProtector login page is presented when accessing the web interface remotely, and that anonymous or unauthenticated access to administrative functions is not possible.Affected if The SiteProtector interface allows remote access without requiring valid credentials, since the CVE states the attacker must be authenticated.
-
Determine if the SiteProtector interface is exposed to untrusted networksReview network firewall rules, access control lists, or VPN configurations to determine whether the SiteProtector web interface is reachable from networks outside the trusted administrative zone.Affected if The SiteProtector web interface is accessible from untrusted or public networks without additional access controls.
A user is affected if their IBM Security SiteProtector System version is 3.0.x, 3.1.0.x before 3.1.0.4, or 3.1.1.x before 3.1.1.2, and the interface is accessible to remote 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 patches to reach version 3.0.0.7, 3.1.0.4, or 3.1.1.2 as appropriate for the deployed branch. If patching is not immediately feasible, restrict network access to the SiteProtector interface to trusted administrators only.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0161 — 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-2015-0161 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