CVE-2023-33871
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 · uneditedIagona ScrutisWeb versions 2.1.37 and prior are vulnerable to a directory traversal vulnerability that could allow an unauthenticated user to directly access any file outside the webroot.
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 confidenceIagona ScrutisWeb versions 2.1.37 and prior contain a directory traversal vulnerability that allows unauthenticated attackers to access files outside the webroot by manipulating file path inputs. The lack of proper path sanitization enables attackers to use sequences like '../' to navigate the filesystem and read sensitive system files.
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<= 2.1.37CVSS 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.
-
Identify ScrutisWeb installation and versionLocate the ScrutisWeb installation directory and check the version information file, or query the application via its web interface or API for the version number.Affected if The installed version is 2.1.37 or any version prior to it.
-
Determine if the web interface is accessibleConfirm the ScrutisWeb HTTP/HTTPS service is running and reachable on the network. Note the endpoint URL and listening ports.Affected if The web interface is exposed and reachable over the network.
-
Locate file access functionalityIdentify endpoints or parameters within the application that accept file path inputs, particularly those that appear to retrieve or display files.Affected if The application contains functionality that processes user-supplied file paths without proper validation.
-
Test path traversal vulnerabilitySend a request to the identified file access endpoint using path traversal sequences such as '../' to attempt to access files outside the webroot directory.Affected if The application allows traversal sequences and returns file contents from directories outside the webroot.
-
Verify unauthenticated access requirementAttempt the path traversal attack without providing any authentication credentials or session tokens.Affected if The vulnerability is exploitable without authentication, allowing full file access to any user who can reach the service.
The environment is affected if ScrutisWeb version 2.1.37 or prior is installed and the web interface with its file access functionality is accessible, as the path traversal flaw can then be exploited without authentication.
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.
dbcve · scopedImplement strict input validation and path sanitization on all file access endpoints, using canonical path resolution and allowlists to restrict access to intended directories only.
ScrutisWeb version 2.1.38 or later (latest available version)
- Identify the current ScrutisWeb version in use
- Contact Iagona vendor or check their official release notes for version 2.1.38 or later which should contain the directory traversal fix
- Backup the current ScrutisWeb installation and configuration before upgrading
- Upgrade ScrutisWeb to the latest available version (ideally version 2.1.38 or newer)
- Verify the upgrade was successful and test that the directory traversal vulnerability is no longer exploitable
- Ensure the web server is properly configured to restrict file access to the webroot after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33871 — 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-33871 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