CVE-2013-1081
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 MDM.php in Novell ZENworks Mobile Management (ZMM) 2.6.1 and 2.7.0 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 confidenceDirectory traversal vulnerability in MDM.php in Novell ZENworks Mobile Management allows remote attackers to manipulate the language parameter using '..' sequences to access and execute arbitrary local files on the server.
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.6.1= 2.7.0CVSS 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.
-
Identify ZMM installation and versionCheck for Novell ZENworks Mobile Management installation. Common installation paths: Windows: C:\Program Files\Novell\ZENworks\Mobile Management\ or Linux: /opt/novell/zmm/. Look for version information in about.php, version.txt, or the MDM.php file header.Affected if Installed version is exactly 2.6.1 or exactly 2.7.0
-
Locate MDM.php fileSearch for MDM.php in the web root directory of the ZMM installation. On Windows typical path: C:\inetpub\wwwroot\ZENworks\mdm\ or under the web application root. On Linux: /var/www/html/ or the ZMM web directory.Affected if MDM.php exists in the web-accessible directory
-
Verify web accessibility of MDM.phpAttempt to access MDM.php via HTTP/HTTPS from the server or test if the web server serves PHP files from the ZMM directory. Check web server configuration (IIS or Apache) for the ZMM virtual directory or application.Affected if MDM.php is reachable via HTTP/HTTPS from the network
-
Test for directory traversal vulnerabilitySend a crafted HTTP request to MDM.php with language parameter containing traversal sequences such as ../../../../etc/passwd or ..\..\..\windows\system32\config\sam and observe the response for file contents or error messages revealing successful traversal.Affected if The language parameter accepts and processes '..' path sequences, allowing file access outside the intended directory
A system is affected if Novell ZENworks Mobile Management version 2.6.1 or 2.7.0 is installed with MDM.php accessible via web and the language parameter permits directory traversal sequences.
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 dataImplement strict input validation on the language parameter to restrict it to whitelisted values, or upgrade to a patched version of ZMM if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1081 — 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-1081 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