CVE-2023-45722
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 · uneditedHCL DRYiCE MyXalytics is impacted by path traversal arbitrary file read vulnerability because it uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory. The product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Potential exploits can completely disrupt or take over the application.
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 DRYiCE MyXalytics contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files on the host system by manipulating file path parameters with ../ sequences. The application fails to properly validate and sanitize external input used to construct file paths, allowing traversal outside the intended restricted directory.
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= 5.9= 6.0= 6.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 MyXalytics versionLocate the MyXalytics installation directory and check version metadata files (such as version.ini, about dialog, or the application's main JAR/WAR file properties). On Windows, this may be in Program Files or a custom install path; on Linux, typically under /opt or /app. Alternatively, access the application's web interface and look for a version or About section.Affected if The installed version matches 5.9, 6.0, or 6.1 exactly.
-
Confirm application is accessible via HTTP/HTTPSAttempt to reach the MyXalytics web interface using the base URL (for example, http://hostname:port/myXalytics or similar endpoint). Check if the login or dashboard page loads successfully.Affected if The web interface responds and the version identified in step 1 is 5.9, 6.0, or 6.1.
-
Test for path traversal endpoint exposureUsing a web browser or curl command, attempt a GET request to a suspected file endpoint with a traversal sequence such as /../../../../etc/passwd or similar path pattern, depending on the application's URL structure for file downloads or exports. Observe whether the application returns file contents or an error.Affected if The application returns content from outside its intended directory, confirming the path traversal vulnerability is present.
-
Review access logs for traversal patternsExamine web server or application logs (typically found in logs/ or runtime/logs/ within the installation directory) for entries containing ../ patterns in request parameters. Search for strings like "..%2F" or "../" which indicate traversal attempts.Affected if Log entries show traversal sequences were processed by the application, indicating the vulnerability is reachable.
You are affected if HCL DRYiCE MyXalytics versions 5.9, 6.0, or 6.1 are installed and the application's file path parameter endpoints are accessible over the network.
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 by canonicalizing paths (resolving real paths) and verifying the resolved path remains within the intended base directory before file operations. Reject any input containing traversal sequences (.., /) or use allowlist validation for permitted files/directories.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45722 — 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-45722 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