CVE-2018-17922 json
Circontrol CirCarLife all versions prior to 4.3.1, the PAP credentials of the device are stored in clear text in a log file that is accessi…
published 8y ago modified 4mo ago also EUVD-2018-9663
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Circontrol CirCarLife all versions prior to 4.3.1, the PAP credentials of the device are stored in clear text in a log file that is accessible without authentication.
Patch / fix
- circontrol circarlife_firmware 4.3.1
Is CVE-2018-17922 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-305-03 updated cvss 10.0
Circontrol CirCarLife
-
Circontrol CirCarLife < 4.3.1affected: mitigation “Circontrol has released a new version of the software that is available at (login required):”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
3.25% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- unknown Circontrol CirCarLife all versions prior to 4.3.1
Classification
References
-
securityfocus.com
/bid/105816
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-305-03
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2018-17922
- NVD CVE-2018-17922
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.