dbcve.org
Vnet\/ip Interface PackageApplication · Yokogawa

CVE-2025-48023

MEDIUM · 6.5 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 →
70/100
Remediation priority · Elevated
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 receives maliciously crafted packets, Vnet/IP software stack process may be terminated. 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 denial-of-service vulnerability exists in Yokogawa's Vnet/IP Interface Package software stack. When the affected product receives maliciously crafted packets, the Vnet/IP software stack process terminates unexpectedly, causing service disruption. This affects CENTUM VP R6 and R7 systems running version R1.07.00 or earlier.

MitigationApply the vendor-supplied patch or upgrade to a fixed version of Vnet/IP Interface Package beyond R1.07.00. If immediate patching is not feasible, consider network segmentation and filtering to limit exposure to untrusted packet sources.

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify Vnet/IP Interface Package is installed
    Check for the presence of Yokogawa Vnet/IP software on the system by examining installed programs, program files directory, or running 'Get-ItemProperty' on registry key HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall for Yokogawa entries
    Affected if The Vnet/IP Interface Package software is found on the system
  2. Determine installed Vnet/IP version
    Locate the version information through the Windows Add/Remove Programs panel, the software's About dialog, or by checking the version resource in the Vnet/IP executable files typically located in C:\Program Files\Yokogawa\VnetIP or similar installation directory
    Affected if The version number returned is R1.07.00 or any version prior to R1.08.00
  3. Confirm system is CENTUM VP R6 or R7
    Verify the Yokogawa CENTUM VP version running on the system by checking the CENTUM installation directory or system information, typically found in C:\Program Files\Yokogawa\CENTUM VP
    Affected if The system is running CENTUM VP R6 or CENTUM VP R7
  4. Verify Vnet/IP network exposure
    Check if the Vnet/IP service ports (typically UDP/TCP ports used by Vnet/IP protocol) are listening on network interfaces accessible from untrusted networks using 'netstat -an' or by reviewing firewall rules
    Affected if Vnet/IP ports are exposed to untrusted network segments

The environment is affected if Vnet/IP Interface Package version R1.07.00 or earlier is installed on a CENTUM VP R6 or R7 system, particularly if the Vnet/IP service is network-accessible.

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

Apply the vendor-supplied patch or upgrade to a fixed version of Vnet/IP Interface Package beyond R1.07.00. If immediate patching is not feasible, consider network segmentation and filtering to limit exposure to untrusted packet sources.

Recommended fix Moderate confidence

Vnet/IP Interface Package R1.08.00

  1. Obtain Vnet/IP Interface Package R1.08.00 or later from Yokogawa Electric Corporation's official distribution channels (refer to web-material3.yokogawa.com)
  2. Follow Yokogawa's standard procedures for upgrading the Vnet/IP Interface Package
  3. After upgrade, verify that the Vnet/IP software stack process remains stable and does not terminate upon receiving network packets

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

Fix this in Vnet\/ip Interface Package Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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