CVE-2023-31179
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 · uneditedAgilePoint NX v8.0 SU2.2 & SU2.3 - Path traversal - Vulnerability allows path traversal and downloading files from the server, by an unspecified request.
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 · moderate confidenceAgilePoint NX v8.0 SU2.2 and SU2.3 contain a path traversal vulnerability that allows attackers to traverse directories and download arbitrary files from the server through an unspecified request vector.
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= 8.0CVSS 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 installed AgilePoint NX versionAccess the AgilePoint NX administration portal or check the installation directory for version information. Look for files such as version.txt, about page, or use the admin dashboard to view system information.Affected if The version is exactly 8.0 with SU2.2 or SU2.3 applied.
-
Locate web server logs for the applicationFind the IIS or web server logs for the AgilePoint NX instance. These are typically in C:\inetpub\logs\LogFiles or /var/log/httpd/ depending on the deployment.Affected if Logs contain requests with ../ sequences or path traversal patterns targeting sensitive directories such as ../../windows/win.ini or similar.
-
Check for unauthenticated file download endpointsReview the deployed web application for exposed file download or file access handlers. Look for endpoints that accept file path parameters without proper validation.Affected if File download functionality is accessible without authentication or accepts unvalidated path parameters.
-
Inspect for abnormal file access patternsExamine application and system logs for repeated requests accessing files outside the intended upload or document directories.Affected if There are logged attempts to access system files, configuration files, or directories outside the AgilePoint data folders.
You are affected if your AgilePoint NX installation is version 8.0 with SU2.2 or SU2.3 applied AND file access functionality is exposed without proper path traversal validation.
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 dataImplement strict input validation on file access functions to restrict path traversal sequences (../). Consider applying vendor patches if available and restricting file access to intended directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31179 — 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-31179 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