CVE-2024-22077
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 SQLite database file has weak permissions.
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 Elspec G5 digital fault recorder stores data in an SQLite database file with overly permissive file system permissions. This allows unauthorized local users or processes to read potentially sensitive fault recording data and potentially modify or delete database contents.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Locate the SQLite database file used by G5dfrOn the G5 device, search for .db or .sqlite files, typically in application data directories such as /var/lib/g5dfr, /opt/elspec/data, or paths referenced in the application configuration. Use: find / -name '*.db' -o -name '*.sqlite' 2>/dev/null | xargs ls -la 2>/dev/nullAffected if The database file exists and is found with world-readable or group-readable permissions
-
Check file permissions on the database fileRun ls -la on the identified database file. Examine the permission bits (rwx permissions for owner, group, and others). Use stat for detailed output: stat <database_path>Affected if Permissions show read or write access for 'others' (last three bits contain r--, rw-, r--, -w-, -w-, or rw-) or excessive group permissions
-
Check directory permissions containing the databaseRun ls -ld on the parent directory of the database file: ls -ld <directory_path>. Verify if the directory grants execute permission to unauthorized users, which allows traversal to access the fileAffected if Directory permissions allow access by unauthorized users (others have r-x, rwx, or similar)
-
Verify the G5dfr firmware versionOn the device, check firmware version via command such as: cat /etc/version, uname -a, or the vendor's management interface. Look for version string in application logs or configuration filesAffected if Firmware version is below 1.2.1.12 (for example, 1.2.1.10, 1.2.0.x, or earlier releases)
-
Test unauthorized user access to the databaseIf possible, switch to a non-privileged test user account (or use sudo -u <unauthorized_user>) and attempt: cat <database_path> to read, or echo 'test' >> <database_path> to writeAffected if Non-admin, non-service users can successfully read or modify the database file contents
The environment is affected if the G5dfr firmware version is below 1.2.1.12 AND the SQLite database file or its parent directory has permissive access controls that allow unauthorized local users to read or write the database file.
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
Apply restrictive file permissions to the SQLite database file and its directory, ensuring only the application service account and authorized administrators have read/write access.
G5dfr Firmware 1.2.1.12 or later
- Obtain the G5dfr firmware version 1.2.1.12 or later from Elspec Ltd (www.elspec-ltd.com)
- Apply the firmware upgrade following the vendor's standard firmware update procedure for the G5 digital fault recorder
- After upgrading, verify that the SQLite database file permissions have been strengthened (e.g., restricted read/write access to authorized users/roles only)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22077 — 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-22077 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