CVE-2017-9664
No exploitation reported by the sources we read.
- Published2018-05-24
- WeaknessCWE-22 · CWE-23
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In ABB SREA-01 revisions A, B, C: application versions up to 3.31.5, and SREA-50 revision A: application versions up to 3.32.8, an attacker may access internal files of ABB SREA-01 and SREA-50 legacy remote monitoring tools without any authorization over the network using a HTTP request which refers to files using ../../ relative paths. Once the internal password file is retrieved, the password hash can be identified using a brute force attack. There is also an exploit allowing running of commands after authorization.
Timeline
dates in UTC- 2018-05-2420:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-9664?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-9664?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.31 | ≤ 3.31.5 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.32 | ≤ 3.32.8 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
ABB SREA-01 and SREA-50
SREA-01 revisions A B C: application versions up to 3.31.5 · SREA-50 revision A: application versions up to 3.32.8
Fix
- Mitigation from the vendor CISA ICSA-17-222-05 · 2 productsHMS Industrial Networks Ab created an update to resolve a publicly reported vulnerability in the ABB products listed above. Products are based on a legacy software platform which is no longer actively maintained. The problem is corrected by installing a patch that is available at the following loca…
- Mitigation from the vendor CISA ICSA-17-222-05 · 2 productsNote: ABB has tested the patch only with the latest revisions of the SREA-01. The patch should also be applicable to the latest revisions of the SREA-50. If an old revision of hardware is in use, it is suggested to replace the hardware either with latest revision or with some other remote monitorin…
Advisories and patches
- ics-cert.us-cert.govMitigation
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-23read 2026-10-23
- NVDweakness (CWE)CWE-22read 2026-10-23
- FIRST EPSSEPSS score2.6 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-05-24
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-9664?
Is CVE-2017-9664 actively exploited?
What is the CVSS score for CVE-2017-9664?
Running ABB SREA-01 and SREA-50? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.