# CVE-2018-17922: Information disclosure in Circontrol CirCarLife all versions prior to 4.3.1

> Attackers can read clear-text PAP credentials from an unauthenticated log file, potentially leading to unauthorized access to the charging station.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fwcc-h488-hgmh

## What is CVE-2018-17922?

CVE-2018-17922 is a critical vulnerability in unknown Circontrol CirCarLife all versions prior to 4.3.1, published on 2 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2018-17922?

It affects 1 product.


Products: Circontrol Circarlife Firmware.

## How do I fix CVE-2018-17922?

No fix has been published for CVE-2018-17922 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-17922 being exploited?

There is no known exploitation of CVE-2018-17922 in the wild and no public exploit code.

## Other vulnerabilities in unknown Circontrol CirCarLife all versions prior to 4.3.1

- [CVE-2018-17918](https://insights.sbomify.com/CVE-2018-17918/): Auth bypass in Circontrol CirCarLife all versions prior to 4.3.1 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17922 and fix it if it is affected.

What it is: CVE-2018-17922 is a critical vulnerability in unknown Circontrol CirCarLife all versions prior to 4.3.1, published on 2 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17922 in the wild and no public exploit code.

Affected product: unknown Circontrol CirCarLife all versions prior to 4.3.1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-17922/ (Markdown: https://insights.sbomify.com/CVE-2018-17922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-17922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-17922
- OSV: https://osv.dev/vulnerability/CVE-2018-17922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-17922/
Summaries are generated and may contain mistakes; the official description above is the record.