CVE-2025-66598
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. This product supports old SSL/TLS versions, potentially allowing an attacker to decrypt communications with the web server. 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 · high confidenceThe FAST/TOOLS product suite (packages RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) versions R9.01 through R10.04 supports outdated SSL/TLS protocol versions (likely SSLv3, TLS 1.0, or TLS 1.1) with known cryptographic weaknesses. This allows attackers to potentially decrypt communications with the web server through attacks such as POODLE or BEAST.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 FAST/TOOLS installation and versionLocate the FAST/TOOLS installation directory and check for version information files, typically found in the product installation folder or via system inventory tools that enumerate Yokogawa software.Affected if Installed version falls within R9.01 through R10.04 inclusive.
-
Confirm web server components are runningIdentify if any of the affected web components (RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) are currently running as services or processes, particularly on ports 80, 443, or custom web service ports.Affected if Any of these web-facing components are active and listening on network ports.
-
Check SSL/TLS protocol configurationUse an SSL/TLS scanning tool (such as nmap with ssl-enum-ciphers or testssl.sh) against the web server ports to enumerate supported protocols. Alternatively, review the web server configuration files for protocol version settings.Affected if The scan reveals support for SSLv3, TLS 1.0, or TLS 1.1 protocols.
-
Verify weak cipher suites are enabledAnalyze the SSL/TLS scan results or configuration files to identify if weak cipher suites (such as those using RC4, 3DES, or export-grade ciphers) are enabled alongside the outdated protocols.Affected if Weak cipher suites are listed as supported in the SSL/TLS handshake negotiation.
A user is affected if FAST/TOOLS versions R9.01-R10.04 are installed with any of the web components active and the server accepts connections using SSLv3, TLS 1.0, or TLS 1.1 protocols.
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 dataDisable weak SSL/TLS protocols (SSLv3, TLS 1.0, TLS 1.1) in the affected web server configurations and enforce TLS 1.2 or higher only. Verify configuration changes with SSL/TLS scanning tools.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66598 — 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-66598 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