CVE-2023-29121
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 TCF Agent service could be used to get 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 · low confidenceThe Waybox Enel TCF Agent service contains a vulnerability that allows an authenticated attacker to escalate privileges to administrator level on the Waybox system. The specific technical details of the exploitation mechanism are not publicly documented in available sources.
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 TCF Agent serviceCheck if the Waybox Enel TCF Agent service is running on the system. Look for processes named 'tcf-agent', 'waybox-tcf', or similar in the process list. On Linux check: ps aux | grep -i tcf. On embedded devices, check /proc/ for running processes.Affected if The TCF Agent service is present and running on the system
-
Check firmware versionRetrieve the installed firmware version of the Enelx Waybox Pro device. This is typically found in the device web interface under 'Settings' > 'System' > 'Firmware Version', or via CLI command such as 'cat /etc/version', 'fw_printenv', or checking /proc/cmdline. Compare the version string to the affected range: < 2.1.1.0_jb3vu096a.Affected if The installed firmware version is less than 2.1.1.0_jb3vu096a
-
Verify TCF Agent authentication configurationExamine the TCF Agent configuration files for authentication settings. Look for configuration files in /etc/tcf/, /opt/waybox/config/, or similar paths. Check if authentication is enforced for TCF Agent connections and verify that default or weak credentials are not in use.Affected if TCF Agent authentication is disabled, using default credentials, or improperly configured allowing unauthorized access
-
Review TCF Agent access logsInspect TCF Agent service logs for privilege escalation indicators. Look for logs in /var/log/tcf/, /var/log/waybox/, or system logs (syslog, journalctl). Search for events indicating administrator role assignment, privilege changes, or unusual authenticated actions.Affected if Logs show unauthorized administrator role assignments or privilege escalation events from non-admin accounts
A system is affected if it runs Enelx Waybox Pro firmware versions below 2.1.1.0_jb3vu096a with the TCF Agent service enabled and accessible to authenticated users.
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 available vendor patches for the Waybox Enel TCF Agent. If no patch exists, restrict access to the TCF Agent service to trusted administrative personnel only and monitor for unauthorized privilege escalation attempts.
Waybox Pro Firmware 2.1.1.0_jb3vu096a
- 1. Identify the current firmware version of the Waybox Pro device
- 2. Access the Waybox Pro administrative interface or use the firmware update mechanism
- 3. Download the Waybox Pro Firmware version 2.1.1.0_jb3vu096a or later from the official Enel X support site (support-emobility.enelx.com)
- 4. Apply the firmware update following the manufacturer's documented upgrade procedure
- 5. Verify the upgrade was successful by confirming the new firmware version
- 6. Validate that the TCF Agent service now properly enforces access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29121 — 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-29121 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