Path TraversalWeakness · CWE-22

CVE-2024-27575

HIGH · 7.5 CVSS v3.1 Published 2024-04-04
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
INOTEC Sicherheitstechnik WebServer CPS220/64 3.3.19 allows a remote attacker to read arbitrary files via absolute path traversal, such as with the /cgi-bin/display?file=/etc/passwd URI.

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

The INOTEC CPS220/64 WebServer version 3.3.19 contains a path traversal vulnerability in its CGI binary at /cgi-bin/display. The application fails to sanitize user-supplied input in the 'file' parameter, allowing remote attackers to read arbitrary files on the filesystem using absolute paths (e.g., /etc/passwd). This is a classic directory traversal vulnerability exploitable without authentication.

MitigationImplement strict input validation and whitelisting for the file parameter to prevent path traversal sequences. Restrict the web server process to allowed directories and apply principle of least privilege. If available, apply vendor patch for version 3.3.19 or later.

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 INOTEC CPS220/64 WebServer version
    Locate the web server binary or check the HTTP Server header in responses. Common paths may include /usr/sbin/, /opt/, or the application's installation directory. Run 'httpd -v' or equivalent if available, or examine the login/admin interface for a version display.
    Affected if The installed version is 3.3.19 or falls within the 3.3.x branch where the vulnerability exists.
  2. Confirm the CGI binary /cgi-bin/display is accessible
    Send a request to http://target/cgi-bin/display (without parameters) or check if the endpoint returns a valid response (even an error) rather than a 404. Use curl or a browser to test.
    Affected if The /cgi-bin/display endpoint responds (returns any HTTP status other than 404 or connection failure), indicating the CGI interface is enabled.
  3. Test path traversal vulnerability on the file parameter
    Send a crafted request to http://target/cgi-bin/display?file=/etc/passwd (or a similar sensitive file appropriate to the OS). Use curl: curl 'http://TARGET/cgi-bin/display?file=/etc/passwd'. If the response contains the contents of /etc/passwd (root user entries), the vulnerability is present.
    Affected if The response returns the contents of /etc/passwd or another arbitrary file specified via absolute path, confirming the path traversal is exploitable.
  4. Verify web server runs without authentication protection
    Confirm that the /cgi-bin/display endpoint is reachable without providing any credentials. Send a request from an unauthenticated context and verify it processes the request.
    Affected if The CGI endpoint processes requests without requiring authentication, allowing unauthenticated attackers to exploit the flaw.

You are affected if the INOTEC CPS220/64 WebServer version 3.3.19 (or any 3.3.x version) is running with the /cgi-bin/display CGI endpoint accessible, and unauthenticated requests to this endpoint can read arbitrary files via the file parameter.

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

Implement strict input validation and whitelisting for the file parameter to prevent path traversal sequences. Restrict the web server process to allowed directories and apply principle of least privilege. If available, apply vendor patch for version 3.3.19 or later.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27575 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