# CVE-2018-17918: Auth bypass in Circontrol CirCarLife all versions prior to 4.3.1

> Attackers can bypass authentication on CirCarLife EV charging stations by accessing a specific URL, allowing unauthorized access to the device.

- **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-jhc3-4262-c357

## What is CVE-2018-17918?

CVE-2018-17918 is a critical authentication bypass 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, authentication to the device can be bypassed by entering the URL of a specific page.

Weakness: CWE-287 (Improper Authentication), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Circontrol Circarlife Firmware.

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

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

## Is CVE-2018-17918 being exploited?

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

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

- [CVE-2018-17922](https://insights.sbomify.com/CVE-2018-17922/): Information disclosure 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-17918 and fix it if it is affected.

What it is: CVE-2018-17918 is a critical authentication bypass 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-17918 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-17918/ (Markdown: https://insights.sbomify.com/CVE-2018-17918/index.md)
```

## Sources

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

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