dbcve.org
Circarlife FirmwareOperating system · Circontrol

CVE-2018-17918

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-02
Fix available
A fix is available. Upgrade to 4.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Circontrol CirCarLife all versions prior to 4.3.1, authentication to the device can be bypassed by entering the URL of a specific page.

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 · moderate confidence

The CirCarLife web application suffers from an authentication bypass vulnerability where accessing certain pages directly via URL allows unauthenticated access to sensitive functionality. This broken access control issue enables attackers to bypass the login mechanism entirely, potentially exposing administrative functions and device controls.

MitigationUpgrade CirCarLife to version 4.3.1 or later to obtain the patched authentication logic. If immediate patching is not possible, restrict network access to the device management interfaces via firewall rules or network segmentation to minimize exposure.

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
Circarlife FirmwareOperating system
Affected:< 4.3.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CirCarLife web application presence
    Access the device's web interface by navigating to the device IP address on port 80 or 443. Look for CirCarLife branding, login page, or charging station management interface.
    Affected if The CirCarLife web interface is accessible on the network.
  2. Determine firmware version
    Check the firmware version displayed in the web interface footer, system info page, or about section. If authenticated access is possible, log in and navigate to settings or status pages to locate the version number.
    Affected if The displayed firmware version is lower than 4.3.1.
  3. Test unauthenticated access to sensitive endpoints
    Attempt to access common administrative paths directly without logging in. Examples include /admin, /status, /config, /settings, or /diagnostics pages by constructing URLs like http://[device-ip]/admin or http://[device-ip]/status.
    Affected if Sensitive pages load successfully without requiring login credentials.
  4. Verify authentication enforcement on login page
    Observe whether the login page properly redirects unauthenticated users or returns to a login prompt when accessing protected resources. Attempt to access multiple device control or configuration URLs directly.
    Affected if Protected pages are accessible without any authentication token or session.

The environment is affected if the CirCarLife web interface is exposed and the firmware version is below 4.3.1, or if administrative pages can be accessed without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.3.1 or later
Fixed in 4.3.1
Interim mitigation

Upgrade CirCarLife to version 4.3.1 or later to obtain the patched authentication logic. If immediate patching is not possible, restrict network access to the device management interfaces via firewall rules or network segmentation to minimize exposure.

Recommended fix Moderate confidence

4.3.1

  1. Upgrade Circarlife (Circontrol CirCarLife) firmware to version 4.3.1 or later to address the authentication bypass vulnerability (CWE-288).
  2. After upgrading, verify that the authentication bypass vulnerability is resolved by attempting to access protected pages without proper credentials.
  3. Confirm that the web interface now properly requires authentication before granting access to sensitive pages.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Circarlife Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-17918 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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