CVE-2025-3498
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 · uneditedAn unauthenticated user with management network access can get and modify the Radiflow iSAP Smart Collector (CentOS 7 - VSAP 1.20) configuration. The device has two web servers that expose unauthenticated REST APIs on the management network (TCP ports 8084 and 8086). An attacker can use these APIs to get access to all system settings, modify the configuration and execute some commands (e.g., system reboot).
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 Radiflow iSAP Smart Collector (VSAP 1.20 on CentOS 7) exposes two unauthenticated REST APIs on TCP ports 8084 and 8086 accessible via the management network. These APIs allow any unauthenticated user to retrieve all system settings, modify configurations, and execute commands such as system reboot.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L
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.
-
Confirm Radiflow iSAP Smart Collector installationLocate the installation directory or check running services for VSAP or iSAP components. On CentOS 7, check /opt/radiflow or look for 'vsap' processes via 'ps aux | grep -i vsap'.Affected if The product Radiflow iSAP Smart Collector (VSAP) is installed on the system.
-
Identify listening ports 8084 and 8086Run 'netstat -tlnp | grep -E "8084|8086"' or 'ss -tlnp | grep -E "8084|8086"' to check if the vulnerable REST API ports are open and listening.Affected if TCP ports 8084 or 8086 are in LISTEN state on the system.
-
Verify API accessibility without authenticationFrom a management network host, attempt to access the REST endpoints: curl http://<target>:8084/api/ and curl http://<target>:8086/api/. Check if responses are returned without requiring login credentials.Affected if The REST APIs on ports 8084 and 8086 respond without requiring any authentication.
-
Check network exposure of management portsReview firewall rules (iptables -L -n or firewall-cmd --list-all) to determine if ports 8084 and 8086 are exposed to untrusted networks. Verify the binding address (0.0.0.0 vs 127.0.0.1).Affected if Ports 8084 and 8086 are bound to 0.0.0.0 or allowed through firewall to untrusted networks.
-
Confirm iSAP version is 1.20Check the installed version via 'rpm -qa | grep -i vsap' or inspect version files in the installation directory to confirm it matches the affected version VSAP 1.20.Affected if The installed version is VSAP 1.20 on CentOS 7.
A user is affected if the Radiflow iSAP Smart Collector VSAP 1.20 is installed with ports 8084 or 8086 open and the REST APIs accessible without authentication from their network.
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 dataRestrict access to TCP ports 8084 and 8086 to trusted management IPs only via firewall or network segmentation, and implement authentication/authorization on the exposed REST APIs.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3498 — 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-3498 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