CVE-2023-2880
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 · uneditedFrauscher Sensortechnik GmbH FDS001 for FAdC/FAdCi v1.3.3 and all previous versions are vulnerable to a path traversal vulnerability of the web interface by a crafted URL without authentication. This enables an remote attacker to read all files on the filesystem of the FDS001 device.
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 confidenceThe FDS001 web interface contains a path traversal vulnerability (CWE-22) that allows unauthenticated remote attackers to read arbitrary files on the device filesystem via specially crafted URLs containing '../' sequences.
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<= 1.3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FDS001 product installationIdentify if Frauscher Frauscher Diagnostic System 101 software is installed on the target system. Check for FDS001 service processes, installed applications, or device documentation indicating this product.Affected if The system runs Frauscher Diagnostic System 101 software.
-
Determine installed versionLocate the FDS001 version information through the web interface login page, system diagnostics, installed software list, or product documentation. Compare the version number against the affected range.Affected if The installed version is 1.3.3 or lower.
-
Verify web interface accessibilityDetermine if the FDS001 web interface (typically on ports 80/443 or configured HTTP/HTTPS port) is reachable from the network. Check firewall rules, network access controls, and interface binding configurations.Affected if The FDS001 web interface is network-accessible.
-
Test for path traversal vulnerabilitySend an HTTP request to the web interface with a path traversal sequence such as '../' or '..%2f' appended to a known valid endpoint. For example: http://[target]/../../etc/passwd or similar path patterns. Observe if the response contains file contents from outside the web root.Affected if The response returns file contents from outside the web server root directory.
The environment is affected if Frauscher Diagnostic System 101 version 1.3.3 or lower is installed with an accessible web interface that allows path traversal via '../' sequences in URLs.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch or upgrade to latest version. If unavailable, implement network segmentation to restrict access to the FDS001 web interface and consider deploying a WAF to filter malicious URL patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2880 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2880 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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