dbcve.org
Vnet\/ip Interface PackageApplication · Yokogawa

CVE-2025-1924

HIGH · 8.2 CVSS v3.1 Published 2026-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges Zero-click

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
A vulnerability has been found in Vnet/IP Interface Package provided by Yokogawa Electric Corporation. If affected product receive maliciously crafted packets, a DoS attack may cause Vnet/IP communication functions to stop or arbitrary programs to be executed. The affected products and versions are as follows: Vnet/IP Interface Package (for CENTUM VP R6 VP6C3300, CENTUM VP R7 VP7C3300) R1.07.00 or earlier

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 confidence

A vulnerability in Yokogawa's Vnet/IP Interface Package allows remote attackers to send maliciously crafted packets that can cause denial of service (DoS) to Vnet/IP communication functions or achieve arbitrary program execution. This affects CENTUM VP R6 and R7 systems running version R1.07.00 or earlier.

MitigationUpgrade Vnet/IP Interface Package to a version newer than R1.07.00. Until patched, implement network segmentation and monitor for suspicious packet traffic to limit exposure to this vulnerability.

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
Vnet\/ip Interface PackageApplication
Affected:< r1.08.00

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/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. Confirm Vnet/IP Interface Package installation
    Locate and identify the Yokogawa Vnet/IP Interface Package software on the system. Check installed programs or product directories for CENTUM VP R6/R7 related components.
    Affected if The Vnet/IP Interface Package is installed on the system.
  2. Determine installed version of Vnet/IP Interface Package
    Use the software's version reporting mechanism (such as 'About' dialog, version info in control panel, or product-specific query command) to obtain the exact installed version number.
    Affected if The installed version is R1.07.00 or earlier (versions prior to R1.08.00).
  3. Verify Vnet/IP communications component is active
    Check if the Vnet/IP communication service or daemon is running. Look for Vnet/IP related processes or services in the system task manager or service console.
    Affected if The Vnet/IP Interface Package service/process is actively running and listening on network ports.
  4. Assess network exposure of Vnet/IP interface
    Identify network ports and interfaces the Vnet/IP component is bound to. Use netstat or equivalent to list listening ports associated with Vnet/IP.
    Affected if The Vnet/IP interface is accessible on network segments accessible to untrusted users (not isolated by firewall or network segmentation).

The system is affected if Vnet/IP Interface Package version R1.07.00 or earlier is installed and the Vnet/IP communication service is running and exposed on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Vnet/IP Interface Package to a version newer than R1.07.00. Until patched, implement network segmentation and monitor for suspicious packet traffic to limit exposure to this vulnerability.

Recommended fix High confidence

Vnet/IP Interface Package R1.08.00

  1. 1. Identify all systems running Vnet/IP Interface Package in the environment
  2. 2. Verify current installed version by checking the application or system documentation
  3. 3. Obtain Vnet/IP Interface Package R1.08.00 from official Yokogawa Electric Corporation sources (web-material3.yokogawa.com or official support channels)
  4. 4. Schedule maintenance window as the upgrade may require system restart
  5. 5. Backup current configuration and data before performing upgrade
  6. 6. Install Vnet/IP Interface Package R1.08.00 following Yokogawa's official installation procedures
  7. 7. After installation, verify the version has been updated correctly
  8. 8. Test Vnet/IP communication functions to ensure normal operation
Caveat Review Yokogawa release notes for R1.08.00 to check for any configuration or compatibility changes with CENTUM VP R6/R7

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

Fix this in Vnet\/ip Interface Package Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1924 — 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-1924 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