CVE-2013-1082
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 · uneditedDirectory traversal vulnerability in DUSAP.php in Novell ZENworks Mobile Management before 2.7.1 allows remote attackers to include and execute arbitrary local files via the language 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 confidenceA directory traversal vulnerability in DUSAP.php within Novell ZENworks Mobile Management versions prior to 2.7.1 allows remote attackers to manipulate the language parameter to perform local file inclusion (LFI), potentially enabling arbitrary local file execution on the affected 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 data<= 2.7.0= 2.6.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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.
-
Verify Novell ZENworks Mobile Management is installedCheck for the product in system inventory, installed programs list, or look for the ZENworks Mobile Management installation directory on the serverAffected if The product is installed on the system
-
Determine the installed version of ZENworks Mobile ManagementLocate the version information in the installation directory, configuration files, or the product's about/management interface. Common paths may include the main installation folder or web server document root for the applicationAffected if The installed version is 2.7.0 or earlier, or exactly version 2.6.1
-
Locate the DUSAP.php fileSearch the web server document root for the file DUSAP.php, which is part of the ZENworks Mobile Management web interfaceAffected if DUSAP.php exists and is accessible via the web server
-
Confirm the language parameter endpoint is accessibleAccess the DUSAP.php file via HTTP/HTTPS and verify the language parameter can be manipulated, for example by attempting a request like DUSAP.php?language=../ (note: do not execute an actual exploit, just verify the parameter accepts input)Affected if The web interface accepts a language parameter without proper validation
-
Check for existing input validation on the language parameterReview any available web application firewall logs, application logs, or configuration files related to the DUSAP.php component to determine if input validation existsAffected if No input validation is found and the language parameter accepts directory traversal sequences
A system is affected if Novell ZENworks Mobile Management version 2.7.0 or earlier (including 2.6.1) is installed and the DUSAP.php file with the language parameter is accessible via the web interface.
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 to Novell ZENworks Mobile Management version 2.7.1 or later, or implement strict input validation on the language parameter to block directory traversal sequences (e.g., ../) and restrict file inclusion to expected locales only.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1082 — 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-1082 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