CVE-2024-22085
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 · uneditedAn issue was discovered in Elspec G5 digital fault recorder versions 1.1.4.15 and before. The shadow file is world readable.
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 Elspec G5 digital fault recorder versions 1.1.4.15 and before have a world-readable shadow file, allowing any local user to read password hashes stored on the device. This permission misconfiguration could enable local privilege escalation if the password hashes are obtained and cracked.
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.2.1.12CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/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.
-
Check firmware version via device interfaceAccess the Elspec G5 device management web interface or CLI and retrieve the firmware version information. This is typically found in System Info, About, or Version settings.Affected if The displayed firmware version is 1.1.4.15 or lower, or any version prior to 1.2.1.12
-
Verify shadow file permissions via shell accessIf you have shell access to the device, run 'ls -la /etc/shadow' or the equivalent password file location to check file permissions.Affected if The file permissions show 'world-readable' (e.g., -r--r--r-- or similar where other users have read permission)
-
Test read access as non-root userIf you can create a limited user account or have access to a low-privilege account on the device, attempt to read the shadow file using 'cat /etc/shadow' or equivalent.Affected if A non-root user can successfully read the shadow file contents and obtain password hashes
You are affected if your G5dfr firmware version is below 1.2.1.12 AND the shadow file is readable by non-privileged users, which allows local privilege escalation.
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 · scoped1.2.1.12
Update the device to a firmware version newer than 1.1.4.15 that corrects the file permissions. If an update is unavailable, disable unused local accounts and implement monitoring for unauthorized access attempts.
Firmware version 1.2.1.12
- Contact Elspec technical support to obtain the firmware upgrade to version 1.2.1.12 or later
- Request and follow the official firmware update procedure from Elspec documentation
- After upgrade, verify that the /etc/shadow file permissions are no longer world-readable (should be 640 or more restrictive)
- Confirm the upgrade was successful by checking the firmware version in the device management interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22085 — 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-22085 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