CVE-2023-29114
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 · uneditedSystem logs could be accessed through web management application due to a lack of access control. An attacker can obtain the following sensitive information: • Wi-Fi access point credentials to which the EV charger can connect. • APN web address and credentials. • IPSEC credentials. • Web interface access credentials for user and admin accounts. • JuiceBox system components (software installed, model, firmware version, etc.). • C2G configuration details. • Internal IP addresses. • OTA firmware update configurations (DNS servers). All the credentials are stored in logs in an unencrypted plaintext format.
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 confidenceThe JuiceBox EV charger's web management application lacks proper access control on log file endpoints, allowing unauthenticated attackers to access system logs. These logs contain sensitive plaintext credentials including Wi-Fi AP credentials, APN details, IPSEC credentials, admin/user web interface credentials, and internal network configuration data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 exposed JuiceBox web management interfaceScan your network for devices running the JuiceBox web interface (typically ports 80/443). Identify the device by checking the HTTP response headers or the login page for JuiceBox branding.Affected if A JuiceBox EV charger web interface is accessible on your network.
-
Verify log endpoint accessibility without authenticationAttempt to access common log paths such as /log, /logs, /system.log, /debug.log, or /status/log via HTTP GET request without providing any credentials. Use a tool like curl: curl -s http://<juicebox-ip>/logAffected if Log file endpoints return content without requiring authentication.
-
Inspect log content for sensitive data exposureIf logs are accessible, examine the response content. Search within the logs for plaintext strings such as 'password', 'PSK', 'WPA', 'APN', 'secret', 'credential', or similar keywords indicating Wi-Fi, IPSEC, or admin credentials.Affected if Logs contain plaintext credentials for Wi-Fi AP, APN, IPSEC, or web interface users.
-
Check network accessibility of the management interfaceDetermine if the JuiceBox web interface is exposed to untrusted networks (not behind VPN, ACL, or firewall). Verify network segment placement and whether external access is possible.Affected if The management interface is reachable from untrusted networks without network-level restrictions.
You are affected if the JuiceBox web management interface has log endpoints accessible without authentication and those logs contain plaintext 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.
From vendor dataImplement authentication and authorization checks on all log access endpoints, and ensure credentials are never stored in plaintext in logs (use masking or hashing).
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29114 — 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-2023-29114 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