CVE-2018-17922
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 · uneditedCircontrol 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.
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 confidenceCircontrol CirCarLife devices before version 4.3.1 store PAP (Password Authentication Protocol) credentials in clear text within a log file. This log file is accessible without any authentication, allowing remote unauthenticated attackers to obtain valid device credentials.
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< 4.3.1CVSS 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.0/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 CirCarLife deviceConfirm the target device is a Circontrol CirCarLife electric vehicle charging station by checking the device model, web interface, or system informationAffected if The device is a Circontrol CirCarLife model
-
Check firmware versionAccess the device's web interface, administrative console, or system settings to retrieve the installed firmware version. Compare this version number against the vulnerable range of < 4.3.1Affected if Firmware version is below 4.3.1
-
Locate the credential log fileAccess the device's file system or log directory to find the log file referenced in the vulnerability. The vulnerability indicates a log file stores PAP credentials and is accessible without authenticationAffected if The log file exists and is accessible without authentication
-
Inspect for clear text credentialsOpen or retrieve the log file content and search for PAP credentials (username/password pairs) stored in plain text format rather than hashed or encryptedAffected if PAP credentials are present in clear text within the log file
A user is affected if they have a CirCarLife device running firmware version below 4.3.1 with accessible log files containing clear text PAP credentials
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.
dbcve · scoped4.3.1
Upgrade CirCarLife firmware to version 4.3.1 or later to remediate the clear text credential storage. Immediately rotate all credentials that may have been exposed, as the log file was accessible without authentication.
Circontrol CirCarLife Firmware 4.3.1
- Identify the current firmware version of the Circontrol CirCarLife charging station
- Download CirCarLife firmware version 4.3.1 or later from the official Circontrol vendor
- Follow the vendor's standard firmware upgrade procedure, typically via the device's web interface or USB update method
- After upgrading, verify that the credentials are no longer stored in clear text in log files
- Confirm that log files are now properly protected and require authentication for access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17922 — 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-2018-17922 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