CVE-2023-29117
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 · uneditedWaybox Enel X web management API authentication could be bypassed and provide administrator’s privileges over the Waybox system.
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 Waybox Enel X web management API has an authentication bypass vulnerability that allows unauthenticated attackers to gain administrator privileges on the Waybox system. This is a critical authentication/authorization failure in the web management interface.
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< 2.1.1.0_jb3vu096aCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Waybox Enel X device in your environmentLocate Waybox Pro hardware devices or systems running Enel X Waybox software. Check device inventory, network scans, or physical inspection for Waybox Pro charging station hardware.Affected if Waybox Enel X device is present in the environment
-
Check installed firmware versionAccess the device administrative interface or check system files/logs for the firmware version string. Look for version numbers in format like 'x.x.x.x_xxxxxxxx'. Compare against the affected range of versions before 2.1.1.0_jb3vu096a.Affected if Firmware version is below 2.1.1.0_jb3vu096a
-
Verify web management API accessibilityTest network connectivity to the device web management interface ports (typically HTTP/HTTPS on the device IP). Attempt to reach the API endpoints used for administrative functions.Affected if Web management API is reachable from network segments accessible to users or attackers
-
Confirm remote administrative access is enabledCheck device configuration settings for remote management or administrative API access. Look for settings that allow remote administrative access, web API exposure, or external connectivity.Affected if Remote administrative access to the web management API is enabled
A user is affected if they have a Waybox Enel X device running firmware below 2.1.1.0_jb3vu096a with the web management API exposed and remote administrative access enabled.
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 · scoped2.1.1.0_jb3vu096a
Apply any vendor-supplied patches for Waybox Enel X immediately; if no patch is available, disable remote administrative access to the web management API and implement additional access controls such as network segmentation, VPN requirements, or IP allowlisting.
2.1.1.0_jb3vu096a
- 1. Identify the current firmware version of the Waybox Pro device through the web management interface or device documentation
- 2. Obtain firmware version 2.1.1.0_jb3vu096a from the official Enel X support source at support-emobility.enelx.com
- 3. Follow the official Waybox Pro firmware update procedure to apply the new firmware version
- 4. Verify the upgrade was successful by confirming the device is running firmware version 2.1.1.0_jb3vu096a
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29117 — 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-29117 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