dbcve.org
Xangati Software ReleaseApplication · Xangati

CVE-2014-0358

HIGH · 7.8 CVSS v2.0 Published 2014-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Multiple directory traversal vulnerabilities in Xangati XSR before 11 and XNR before 7 allow remote attackers to read arbitrary files via a .. (dot dot) in (1) the file parameter in a getUpgradeStatus action to servlet/MGConfigData, (2) the download parameter in a download action to servlet/MGConfigData, (3) the download parameter in a port_svc action to servlet/MGConfigData, (4) the file parameter in a getfile action to servlet/Installer, or (5) the binfile parameter to servlet/MGConfigData.

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 confidence

Multiple directory traversal vulnerabilities exist in Xangati XSR before version 11 and XNR before version 7, allowing remote attackers to read arbitrary files by using '..' sequences in parameters across five different servlet endpoints. The vulnerabilities affect getUpgradeStatus and download actions in servlet/MGConfigData, port_svc action, getfile action in servlet/Installer, and the binfile parameter. This allows unauthenticated remote attackers to access sensitive system files.

MitigationUpgrade Xangati XSR to version 11 or later and XNR to version 7 or later to obtain patched code. If immediate patching is not feasible, consider network segmentation to limit exposure of the vulnerable servlet interfaces and implement web application firewall rules to detect and block directory traversal patterns in HTTP parameters.

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
Xangati Software ReleaseApplication
Affected:all versions
Xangati XnrApplication
Affected:all versions

CVSS 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
Complete
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:C/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Xangati XSR or XNR is installed
    Search for Xangati installation directories or check for running processes named 'xangati', 'xsr', or 'xnr' using commands like 'ps -ef | grep -i xangati' or 'find / -name "*xangati*" -type d 2>/dev/null'
    Affected if Xangati XSR or XNR software is found on the system
  2. Determine the installed version of Xangati XSR
    Look for version information in installation files, configuration files, or the application interface. Check common locations such as /opt/xangati/, /usr/local/xangati/, or the application's help/about section. Look for a version file or check the XSR web interface if accessible.
    Affected if XSR version is found to be lower than version 11 (e.g., 10.x, 9.x, etc.)
  3. Determine the installed version of Xangati XNR
    Look for version information in installation files, configuration files, or the application interface. Check installation directories for version manifests or the application's help/about section.
    Affected if XNR version is found to be lower than version 7 (e.g., 6.x, 5.x, etc.)
  4. Verify the vulnerable servlet endpoints are exposed
    Check if the web interfaces for servlet/MGConfigData, servlet/Installer, or port_svc are accessible. Look for these paths in web server configuration files (e.g., Apache Tomcat server.xml, web.xml) or test by accessing http://<host>/servlet/MGConfigData or similar URL patterns.
    Affected if The vulnerable servlets (MGConfigData, Installer, port_svc) are accessible via HTTP without authentication
  5. Inspect HTTP parameters for directory traversal protection
    Review web application firewall logs, intrusion detection logs, or proxy logs for attempts containing '..' sequences in parameters like 'download', 'getfile', 'getUpgradeStatus', 'port_svc', or 'binfile'. Also check if the application validates or sanitizes these parameters.
    Affected if Directory traversal patterns ('..') in the mentioned parameters are not being blocked or sanitized, or if historical attack attempts are found in logs

A system is affected if Xangati XSR version is below 11 or XNR version is below 7, and the vulnerable servlet endpoints (MGConfigData, Installer, port_svc) handling file download operations are exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Xangati XSR to version 11 or later and XNR to version 7 or later to obtain patched code. If immediate patching is not feasible, consider network segmentation to limit exposure of the vulnerable servlet interfaces and implement web application firewall rules to detect and block directory traversal patterns in HTTP parameters.

Fix this in Xangati Software Release Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0358 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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