CVE-2013-1093
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 · uneditedOpen redirect vulnerability in the fwdToURL function in the ZCC login page in zcc-framework.jar in Novell ZENworks Configuration Management (ZCM) 11.2 before 11.2.3a Monthly Update 1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via the directToPage 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 confidenceOpen redirect vulnerability in the fwdToURL function in the ZCC login page of Novell ZENworks Configuration Management (zcc-framework.jar). The directToPage parameter is not properly validated, allowing remote attackers to craft malicious URLs that redirect users to arbitrary external websites for phishing attacks.
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= 11.2= 11.2.1= 11.2.2= 11.2.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 ZCM installation and versionCheck installed ZENworks Configuration Management version via system inventory or package manager. On Windows, check Add/Remove Programs or registry. On Linux, run 'rpm -qa | grep zenworks' or similar package query.Affected if Version is 11.2, 11.2.1, 11.2.2, or 11.2.3 (not patched to 11.2.3a or later)
-
Locate zcc-framework.jarFind the zcc-framework.jar file in the ZCM installation directory, typically under the ZCC web application path such as $ZENWORKS_HOME/share/tomcat/webapps/zenworks/ or similar path depending on installation.Affected if zcc-framework.jar exists and corresponds to an unpatched ZCM 11.2.x version
-
Verify ZCC web interface is accessibleAccess the ZCC login page via browser or curl at the standard ZCC URL path (commonly /zenworks/zcc or /zcc) on the ZCM server.Affected if ZCC login page is reachable and responds successfully
-
Test redirect vulnerability with directToPage parameterSend a crafted request to the ZCC login page with an external URL in the directToPage parameter, such as: GET /zenworks/zcc?directToPage=http://example.com. Observe if the response performs a redirect to the external domain.Affected if The server redirects to an arbitrary external domain specified in the directToPage parameter rather than validating against an allowed whitelist or rejecting the request
If ZCM 11.2.x is installed and the directToPage parameter on the ZCC login page redirects to user-controlled external URLs, the environment is vulnerable to CVE-2013-1093.
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 dataUpdate to ZCM 11.2.3a Monthly Update 1 or later to patch the vulnerable fwdToURL function in zcc-framework.jar.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1093 — 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-2013-1093 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