CVE-2023-28127
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 path traversal vulnerability exists in Avalanche version 6.3.x and below that when exploited could result in possible information disclosure.
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 confidenceA path traversal vulnerability in Avalanche versions 6.3.x and below allows attackers to access files outside the intended directory through manipulated path inputs, potentially exposing 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<= 6.3.4.153CVSS 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 Avalanche versionCheck the Avalanche server version through the web administration console (typically at /admin or /AvalancheConsole) or by reviewing version information in the software itselfAffected if The installed version is 6.3.4.153 or any version in the 6.3.x line at or below 6.3.4.153
-
Verify web interface accessibilityConfirm that the Avalanche web interface is accessible and exposed (check network listeners, firewall rules, or IIS/Apache/nginx configuration for Avalanche-related virtual directories)Affected if The Avalanche web interface is publicly or loosely accessible on the network
-
Review file access logs for traversal patternsExamine Avalanche server logs for unusual path requests containing sequences like ../, ..\, or absolute paths that may indicate traversal attemptsAffected if Log entries show requests with path traversal sequences pointing outside the expected Avalanche file directories
-
Check for unauthorized file access indicatorsReview server file system logs or Avalanche audit logs for file read operations on system directories (such as /windows/, /etc/, /root/) or configuration files outside the application directoryAffected if File access records show retrieval of files from directories outside the Avalanche application root
A system is affected if Ivanti Avalanche version 6.3.4.153 or any 6.3.x version at or below that build is installed and the web-facing file path functionality is accessible.
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 dataUpgrade Avalanche to a version beyond 6.3.x that contains the security patch; implement strict input validation and canonicalization on file path parameters to prevent traversal sequences.
- Consultation4.0 h
- Implementation12.0 h
- Testing10.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 $8,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28127 — 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-28127 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