CVE-2015-0780
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 the GetReRequestData method of the GetStoredResult class in Novell ZENworks Configuration Management (ZCM) allows remote attackers 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 · high confidenceSQL injection vulnerability in the GetReRequestData method of the GetStoredResult class in Novell ZENworks Configuration Management allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The vulnerability is remotely exploitable without authentication, enabling complete compromise of the database and potentially the underlying 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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Confirm ZCM installationCheck for running Novell ZENworks Configuration Management processes (e.g., zenserver, zcmapp) or look for ZCM installation directories on the system.Affected if ZCM is installed and running on the system
-
Identify ZCM management interfacesIdentify which network interfaces and ports the ZCM services are listening on (typically ports 443 or 80 for the management web console).Affected if The ZCM management interface is bound to a network-accessible IP address rather than localhost only
-
Verify network exposureCheck firewall rules and network accessibility of ZCM management ports from untrusted networks. Determine if the ZCM server is directly reachable from the internet or untrusted LAN segments.Affected if ZCM management ports are accessible from untrusted network segments or the internet
-
Confirm vulnerability applicabilitySince all versions of Novell ZENworks Configuration Management are affected by CVE-2015-0780, verify that the ZCM web component (handling GetStoredResult class requests) is enabled and accessible.Affected if The ZCM web management interface is enabled and reachable over the network
If Novell ZENworks Configuration Management is installed and its management interface is network-accessible, the environment is affected by CVE-2015-0780 because all versions contain the SQL injection vulnerability in the GetReRequestData method.
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 the vendor patch for CVE-2015-0780 immediately. If no patch is available, restrict network access to ZCM management interfaces via firewall and disable the affected component until a fix can be applied. Implement input validation and parameterized queries as part of the remediation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0780 — 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-0780 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