CVE-2025-66602
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 · uneditedA vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. The web server accepts access by IP address. When a worm that randomly searches for IP addresses intrudes into the network, it could potentially be attacked by the worm. The affected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04
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 confidenceThe FAST/TOOLS web server accepts connections based solely on IP address without additional authentication or access control verification. When exposed to network segments accessible by worms scanning random IP addresses, the server can be directly attacked.
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>= r9.01, <= r10.04CVSS 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 if Yokogawa Fast/TOOLS is installedCheck for Fast/TOOLS software components or services on the system. Look for processes named 'FAST/TOOLS', 'FastTools', or related web server processes. Consult system inventory or installed software lists.Affected if Fast/TOOLS software is found on the system
-
Determine the installed Fast/TOOLS versionUse system administration tools, check installed program version information, or look for version details in Fast/TOOLS documentation or configuration files. Compare the version against the affected range: r9.01 through r10.04.Affected if Installed version falls within r9.01 to r10.04 inclusive
-
Verify if the Fast/TOOLS web server is network-accessibleCheck network configuration, firewall rules, and listening ports (typically HTTP/HTTPS ports used by Fast/TOOLS web interface). Determine if the web server bind address allows connections from untrusted network segments.Affected if Web server accepts connections from network segments accessible to untrusted or random IP addresses
-
Confirm whether IP-based authentication is the sole access controlReview Fast/TOOLS web server configuration and authentication settings. Determine if access is granted purely based on source IP address without additional username/password, token, or multi-factor authentication.Affected if IP address is the only authentication mechanism enforced for web server access
The environment is affected if Fast/TOOLS version r9.01 through r10.04 is installed and the web server is accessible from untrusted network segments with IP-based authentication as the sole access control.
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 proper authentication mechanisms and network segmentation to restrict web server access. Apply firewall rules to limit exposure to trusted IPs only, and upgrade to patched versions when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66602 — 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-66602 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