dbcve.org
ShocklineApplication · Anritsu

CVE-2025-7976

HIGH · 7.8 CVSS v3.0 Published 2025-09-02
Fix available
A fix is available. Upgrade to 2025.4.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Anritsu ShockLine CHX File Parsing Deserialization of Untrusted Data 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 user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26882.

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 confidence

The vulnerability exists in Anritsu ShockLine's CHX file parser, which deserializes data from CHX files without proper validation of user-supplied data. This unsafe deserialization allows attackers to execute arbitrary code in the context of the current process by crafting malicious CHX files that victims must open.

MitigationDo not open CHX files from untrusted sources; apply vendor-provided patches when available; consider application sandboxing or network isolation to limit exposure.

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
ShocklineApplication
Affected:< 2025.4.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Anritsu ShockLine is installed
    Search the system for Anritsu ShockLine application directories or check installed programs list for 'Anritsu' or 'ShockLine' entries
    Affected if Anritsu ShockLine software is present on the system
  2. Determine the installed version
    Locate the ShockLine application and check its version information, typically found in the executable properties, about dialog, or installation directory
    Affected if The installed version is less than 2025.4.2 (the version number shown is below 2025.4.2)
  3. Identify CHX file handling capability
    Determine if the installed ShockLine instance can open or process CHX files, which is the affected file format for this vulnerability
    Affected if CHX file import or processing features are available in the installed version
  4. Assess CHX file exposure
    Review whether users routinely open CHX files from external sources, network shares, or email attachments
    Affected if Users open CHX files from untrusted or external sources without verification
  5. Check for indicators of compromise
    Examine the system for any unexpected or newly created CHX files, especially in download folders or recent documents, and review any antivirus alerts related to ShockLine or CHX files
    Affected if Suspicious CHX files are found or security alerts exist related to this software

A system is affected if Anritsu ShockLine version 2025.4.2 or earlier is installed and users can open CHX files, since the vulnerability requires processing a malicious CHX file to trigger unsafe deserialization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.4.2 or later
Fixed in 2025.4.2
Interim mitigation

Do not open CHX files from untrusted sources; apply vendor-provided patches when available; consider application sandboxing or network isolation to limit exposure.

Recommended fix High confidence

ShockLine 2025.4.2 or later

  1. Identify the current installed version of Anritsu ShockLine software
  2. Navigate to the official Anritsu support website or contact Anritsu directly to obtain version 2025.4.2 or later
  3. Download the ShockLine version 2025.4.2 or the latest stable release
  4. Close any running instances of the ShockLine software
  5. Install the updated version following standard installation procedures
  6. Verify the installed version matches or exceeds 2025.4.2
  7. Exercise caution when opening CHX files from untrusted sources

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shockline Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7976 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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