dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-31801

HIGH · 7.5 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Directory Traversal vulnerability in NEXSYS-ONE before v.Rev.15320 allows a remote attacker to obtain sensitive information via a crafted request.

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 · moderate confidence

Directory traversal vulnerability in NEXSYS-ONE before v.Rev.15320 allows remote attackers to access sensitive files outside the web root directory using '../' traversal sequences in crafted HTTP requests, potentially exposing configuration files, credentials, or other confidential data.

MitigationUpgrade NEXSYS-ONE to v.Rev.15320 or later to obtain the patch for this directory traversal vulnerability. If immediate upgrade is not possible, implement input validation and path sanitization filters to block traversal sequences in user-supplied requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 NEXSYS-ONE is installed
    Search for NEXSYS-ONE processes running on the system or check installed applications directory. Look for process names or service entries containing 'NEXSYS-ONE'.
    Affected if NEXSYS-ONE is not found on the system, the vulnerability does not apply.
  2. Determine installed NEXSYS-ONE version
    Locate the version information for the installed NEXSYS-ONE instance. Common methods include: checking the application UI help/about section, querying the service banner, or inspecting version files in the installation directory. Look for a version string in format v.Rev.xxxxx or similar.
    Affected if Unable to determine the version; manual verification required.
  3. Compare version to affected range
    Compare your identified version against v.Rev.15320. Versions earlier than v.Rev.15320 (such as v.Rev.15000, v.Rev.14000, etc.) are affected by this directory traversal vulnerability.
    Affected if Installed version is earlier than v.Rev.15320, indicating the system is vulnerable.
  4. Verify web component is enabled
    Confirm the NEXSYS-ONE web interface or API service is running and accessible. This vulnerability is exploitable through HTTP requests, so the web component must be enabled for the flaw to apply.
    Affected if Web interface is disabled or not accessible, the traversal attack surface may be reduced but the underlying vulnerable code may still exist.

If NEXSYS-ONE is installed with a version earlier than v.Rev.15320 and the web interface is accessible, the environment is affected by this directory traversal vulnerability.

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 NEXSYS-ONE to v.Rev.15320 or later to obtain the patch for this directory traversal vulnerability. If immediate upgrade is not possible, implement input validation and path sanitization filters to block traversal sequences in user-supplied requests.

Recommended fix Moderate confidence

v.Rev.15320 or later

  1. Identify the current installed version of NEXSYS-ONE
  2. If the current version is earlier than v.Rev.15320, plan for upgrade to v.Rev.15320 or later
  3. Backup the current NEXSYS-ONE installation and configuration
  4. Obtain the v.Rev.15320 or newer release from official NEXSYS-ONE distribution channels
  5. Follow vendor documentation for upgrading NEXSYS-ONE to the new version
  6. After upgrade, verify the installation is functional
  7. Confirm the path traversal vulnerability is resolved by testing with benign traversal attempts

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

Have this fixed 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-2024-31801 — 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-2024-31801 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