CVE-2025-7975
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 · uneditedAnritsu ShockLine CHX File Parsing Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Anritsu ShockLine. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of CHX files. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-26913.
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 confidenceThis is a directory traversal vulnerability in Anritsu ShockLine's CHX file parser. The application fails to validate user-supplied paths before performing file operations, allowing an attacker to craft a malicious CHX file that can write or access files outside the intended directory. This can be leveraged to achieve remote code execution in the context of the current user.
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< 2025.4.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Locate Anritsu ShockLine installationCheck common installation directories such as C:\Program Files\Anritsu\ or search for 'ShockLine' in your program's directory. Look for the main executable (often named ShockLine.exe or similar).Affected if Anritsu ShockLine software is installed on the system
-
Determine installed versionRight-click the main ShockLine executable, select Properties, and check the Version tab. Alternatively, look for a version file in the installation directory or check the application's About/Help section.Affected if The version number is lower than 2025.4.2 (e.g., 2025.3.1, 2024.x.x, etc.)
-
Verify CHX file parser functionalityCheck if the CHX file import/parser module is present and accessible within the application. Look for options to import, open, or process .chx files in the application's file menu or toolbar.Affected if CHX file parsing capability exists and is available for use
-
Review recent file processing activityExamine application logs, recent files lists, or the application's working directory for evidence of .chx files that have been opened or processed.Affected if CHX files have been opened or processed in the application
You are affected if Anritsu ShockLine is installed with a version lower than 2025.4.2 and the CHX file parser feature is or has been used to process files.
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 · scoped2025.4.2
Avoid opening CHX files from untrusted sources. Apply vendor patches when available. Consider network segmentation and least-privilege user contexts as compensating controls.
2025.4.2 or later
- Obtain the fixed version of Anritsu ShockLine software (version 2025.4.2 or later) from the official Anritsu vendor
- Download the updated ShockLine software from Anritsu's official source or contact their support
- Install the updated version following Anritsu's standard installation procedures
- Verify the installation completed successfully and the version number reflects 2025.4.2 or later
- Restart any running instances of the ShockLine software to ensure the patched version is fully active
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-7975 — 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-2025-7975 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