dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-37825

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
An issue in EnvisionWare Computer Access & Reservation Control SelfCheck v1.0 (fixed in OneStop 3.2.0.27184 Hotfix May 2024) allows unauthenticated attackers on the same network to perform a directory traversal.

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

EnvisionWare Computer Access & Reservation Control SelfCheck v1.0 contains a directory traversal vulnerability that allows unauthenticated attackers on the same network to access files outside the web root through specially crafted path sequences in HTTP requests.

MitigationApply the OneStop 3.2.0.27184 Hotfix May 2024 to remediate this vulnerability. Additionally, network segmentation should be implemented to restrict access to the affected service to only trusted network segments.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Confirm EnvisionWare SelfCheck installation
    Check for the presence of EnvisionWare SelfCheck software on the system. Common installation paths may include C:\Program Files\EnvisionWare\ or C:\EnvisionWare\. Look for executable files named SelfCheck or related service processes in Task Manager.
    Affected if The software is installed and the version is 1.0 or unpatched (versions prior to the May 2024 hotfix 3.2.0.27184).
  2. Identify installed version number
    Open Windows Registry under HKLM\SOFTWARE\EnvisionWare\ or check the software's About/Version information typically accessible through the application or its service properties. Alternatively, check the version details in Add/Remove Programs.
    Affected if The installed version is 1.0 or falls below the patched version 3.2.0.27184.
  3. Verify web service is enabled
    Check if the SelfCheck web interface service is running. Look for IIS Express, Apache, or the built-in web server process associated with EnvisionWare listening on HTTP/HTTPS ports (commonly port 8080 or 80). Use 'netstat -an' to identify listening ports.
    Affected if The web service is running and accessible, exposing the HTTP interface to network requests.
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the web service port is accessible from network segments other than trusted internal networks. Check if the service binds to 0.0.0.0 or all interfaces versus localhost only.
    Affected if The service port is open to untrusted network segments or the attacker's machine is on the same network as the vulnerable service.
  5. Review HTTP access logs for traversal attempts
    Examine web server access logs for unusual path sequences such as '../', '..\', or absolute path requests outside the web root (e.g., '/..', '/windows/system32'). Log locations may be in the application or web server logs directory.
    Affected if Evidence exists of directory traversal requests targeting system files outside the web root directory.

The environment is affected if EnvisionWare Computer Access & Reservation Control SelfCheck version 1.0 is installed, the web service is enabled and network-accessible, and the system has not been patched with the May 2024 hotfix 3.2.0.27184.

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

Apply the OneStop 3.2.0.27184 Hotfix May 2024 to remediate this vulnerability. Additionally, network segmentation should be implemented to restrict access to the affected service to only trusted network segments.

Recommended fix Moderate confidence

OneStop 3.2.0.27184 Hotfix May 2024

  1. Contact EnvisionWare support to obtain the OneStop 3.2.0.27184 Hotfix May 2024
  2. Apply the hotfix to the affected EnvisionWare Computer Access & Reservation Control SelfCheck v1.0 installation
  3. Verify the patch has been applied successfully by checking the software version
  4. Test the application to confirm the directory traversal vulnerability is remediated
Caveat Consult EnvisionWare release notes for any compatibility considerations before applying the hotfix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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