CVE-2023-37525
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 · uneditedA sensitive information disclosure in HCL BigFix Compliance allows a remote attacker to access files under the WEB-INF directory, which may contain Java class files and configuration information, leading to unauthorized access to application internals.
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 confidenceHCL BigFix Compliance contains a path traversal or insufficient access control vulnerability that allows remote attackers to access files within the WEB-INF directory via direct URL access. This exposes Java class files, configuration descriptors (web.xml), and potentially sensitive application internals that should not be publicly accessible.
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.0.9CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify BigFix Compliance versionLocate the installed HCL BigFix Compliance version number in the application or system inventory, or query the application's about/version endpoint. Compare against the affected version: 2.0.9.Affected if The installed version is exactly 2.0.9.
-
Test WEB-INF directory accessSend an HTTP GET request to the WEB-INF directory via the web application's base URL, for example: http(s)://<hostname>/WEB-INF/ or http(s)://<hostname>/<app>/WEB-INF/. Inspect the HTTP response status code and body.Affected if The server returns HTTP 200 with a directory listing or contents instead of denying access with HTTP 403.
-
Check for exposed web.xmlRequest the web.xml descriptor directly: http(s)://<hostname>/WEB-INF/web.xml or http(s)://<hostname>/<app>/WEB-INF/web.xml. Examine if the XML configuration file is served.Affected if The web.xml file content is returned with HTTP 200, exposing servlet definitions, security constraints, and other deployment descriptors.
-
Verify class file exposureAttempt to access Java class files in the WEB-INF/classes directory, for example: http(s)://<hostname>/WEB-INF/classes/ or specific class file paths. Check if compiled Java classes are downloadable.Affected if Class files are served and downloadable, exposing application logic and potential sensitive class internals.
A user is affected if BigFix Compliance version 2.0.9 is installed AND the web server allows direct HTTP access to the WEB-INF directory or its contents.
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 dataConfigure the web server or application server to deny direct access to the WEB-INF directory, implement proper path traversal protections, and restrict access to sensitive configuration and class files.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37525 — 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-37525 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