CVE-2015-6028
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 · uneditedCastle Rock Computing SNMPc before 2015-12-17 has SQL injection via the sc parameter.
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 confidenceSQL injection vulnerability in Castle Rock Computing SNMPc before the 2015-12-17 patch allows remote attackers to execute arbitrary SQL commands via the sc parameter. The vulnerability stems from improper input validation, enabling attackers to manipulate SQL queries.
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.0= 12.1CVSS 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.
-
Identify SNMPc installation and versionCheck the SNMPc installation directory for version information. Common locations include the installation folder where snmpc.exe resides, or check Windows Programs and Features for Castle Rock SNMPc. The version is typically displayed in the application or in the installation path.Affected if The installed version is 9.0 or 12.1, or any version released before the 2015-12-17 patch date.
-
Verify web interface is enabledCheck the SNMPc configuration for web server or HTTP interface settings. The SQL injection targets the 'sc' parameter, which is a web request parameter. Look for web server configuration in the SNMPc management console or configuration files.Affected if The SNMPc web interface is enabled and accessible.
-
Confirm network exposureDetermine if the SNMPc web service is exposed to network access. Check the binding configuration or firewall rules to see if the web interface listens on external interfaces rather than localhost only.Affected if The SNMPc web interface is reachable from network hosts, allowing remote attackers to send requests with the malicious sc parameter.
You are affected if SNMPc version 9.0 or 12.1 (or any version prior to the 2015-12-17 patch) is installed with the web interface enabled and network-accessible.
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 SNMPc to version 2015-12-17 or later which contains the patch. Alternatively, implement input validation and parameterized queries on the sc parameter as a compensating control until the upgrade can be applied.
- 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-2015-6028 — 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-6028 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