dbcve.org
Xangati Software ReleaseApplication · Xangati

CVE-2014-0359

HIGH · 9.0 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 →
96/100
Remediation priority · Urgent
Remotely reachable 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
Xangati XSR before 11 and XNR before 7 allows remote attackers to execute arbitrary commands via shell metacharacters in a gui_input_test.pl params parameter to servlet/Installer.

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

Xangati XSR before version 11 and XNR before version 7 contain an OS command injection vulnerability in the gui_input_test.pl script accessed via servlet/Installer. Remote attackers can inject arbitrary shell commands by including shell metacharacters in the params parameter, achieving unauthenticated remote code execution with high privileges.

MitigationUpgrade to XSR version 11 or XNR version 7 or later to remediate. As an interim control, restrict network access to the Installer servlet and implement strict input validation on the params parameter until patching is complete.

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 Xangati installation
    Locate Xangati XSR or XNR installation by searching for typical Xangati directories, processes, or services on the system. Common indicators include process names containing 'xangati' or installation folders with 'xangati' in the name.
    Affected if Xangati XSR or XNR software is found running on the system
  2. Determine installed version
    Check the installed version of Xangati XSR or XNR using vendor-provided commands, version files, or the web interface. Compare against the fixed versions: XSR version 11 or XNR version 7.
    Affected if The installed version is XSR before version 11 or XNR before version 7
  3. Locate vulnerable script
    Search for the gui_input_test.pl script in the web application's CGI or scripts directory, typically found within the Xangati installation web root.
    Affected if The gui_input_test.pl script exists in the installation
  4. Check Installer servlet accessibility
    Verify if the /servlet/Installer endpoint is accessible from the network by attempting to access it or reviewing web server access logs for requests to this path.
    Affected if The Installer servlet is reachable over the network without authentication

The environment is affected if Xangati XSR or XNR is installed with a version prior to 11 or 7 respectively, and the Installer servlet with the vulnerable gui_input_test.pl script is network-accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to XSR version 11 or XNR version 7 or later to remediate. As an interim control, restrict network access to the Installer servlet and implement strict input validation on the params parameter until patching is complete.

Recommended fix High confidence

Xangati XSR to version 11+, Xangati XNR to version 7+

  1. 1. Identify the currently installed Xangati XSR and XNR versions in your environment
  2. 2. For Xangati XSR: Upgrade to version 11 or later
  3. 3. For Xangati XNR: Upgrade to version 7 or later
  4. 4. After upgrade, verify the servlet/Installer endpoint no longer accepts shell metacharacters in parameters
  5. 5. Confirm normal application functionality is retained after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xangati Software Release Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0359 — 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-0359 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