SQL Injection in Castle Rock Computing SNMPc (CVE-2015-6028)
Summary
SQL injection in Castle Rock Computing SNMPc (CVE-2015-6028). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Castle Rock Computing SNMPc before 2015-12-17 has SQL injection via the sc parameter.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2015-6028 was discovered in Castle Rock Computing SNMPc.
In plain terms, it is a flaw that lets attackers send rogue commands to the database.
Severity is High (CVSS 8.8/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Castle Rock Computing SNMPc CVE-2015-6028".
CVE-2015-6028 (Castle Rock Computing SNMPc). Severity: High / CVSSv3 8.8. Category: CWE-89.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2015-6028) in Castle Rock Computing SNMPc. In plain words, it is a flaw that lets attackers send rogue commands to the database.
Target versions of Castle Rock Computing SNMPc (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 8.8/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-89)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- advisory community.rapid7.com