CVE-2024-28137
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 · uneditedA local attacker with low privileges can perform a privilege escalation with an init script due to a TOCTOU vulnerability.
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 confidenceA TOCTOU (Time-of-Check-Time-of-Use) race condition in an init script allows a local unprivileged attacker to manipulate the window between a permission/privilege check and the corresponding action, enabling privilege escalation to root or elevated privileges.
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<= 1.5.1<= 1.5.1<= 1.5.1<= 1.5.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 the Charx Sec model numberLocate the device model label or check system information to confirm the device is a Charx Sec 3000, 3050, 3100, or 3150Affected if The device model is one of the four affected models listed in the CVE
-
Check the installed firmware versionAccess the device management interface or use the appropriate firmware version command (e.g., 'fw_printenv', 'cat /etc/version', or via web UI) to retrieve the current firmware versionAffected if The firmware version is 1.5.1 or lower (any version <= 1.5.1)
-
Locate and inspect init scripts for TOCTOU patternsExamine init scripts in /etc/init.d/, /etc/rc.d/, or similar directories for scripts that perform permission checks followed by file operations with a time gap (check the script for separate stat() or access() calls before actual file manipulations)Affected if An init script exists that performs separate privilege/permission checks before taking action, creating a race window
-
Verify the init script runs with elevated privilegesCheck the permissions and ownership of suspected init scripts (ls -la) and determine if they execute as root or with special privilegesAffected if The vulnerable init script runs with root or elevated privileges and is executable on the system
A user is affected if they are running any Charx Sec 3000/3050/3100/3150 device with firmware version 1.5.1 or lower that contains the vulnerable init script with the TOCTOU race condition.
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 dataRefactor the init script to use atomic operations, file locking mechanisms, or perform all necessary checks and actions within a single atomic operation to eliminate the race window.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28137 — 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-2024-28137 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