dbcve.org
G5dfr FirmwareOperating system · Elspec Ltd

CVE-2024-22078

HIGH · 8.8 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 1.2.1.12 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An issue was discovered in Elspec G5 digital fault recorder versions 1.1.4.15 and before. Privilege escalation can occur via world writable files. The network configuration script has weak filesystem permissions. This results in write access for all authenticated users and the possibility to escalate from user privileges to administrative privileges.

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 · high confidence

Elspec G5 digital fault recorder versions 1.1.4.15 and prior contain a privilege escalation vulnerability due to world-writable permissions on the network configuration script. Any authenticated user can modify this script to execute arbitrary code with administrative privileges, achieving privilege escalation from standard user to root/admin access.

MitigationRestrict write permissions on the network configuration script to only authorized administrators (e.g., chmod 755 or chown root:root with appropriate group ownership), and upgrade to a patched version if available from the vendor.

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
G5dfr FirmwareOperating system
Affected:< 1.2.1.12

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device and firmware version
    Access the Elspec G5 web interface or CLI and locate the firmware version information, typically found in System Info, About, or Settings pages
    Affected if Firmware version is 1.1.4.15 or prior, or any version below 1.2.1.12
  2. Locate the network configuration script
    On the Elspec G5 device, find the network configuration script - this is typically a shell script that configures network interfaces, routes, or DNS settings. Common locations include /etc/network/, /scripts/, or within the web interface configuration directories
    Affected if The script exists on the system and is accessible to authenticated users
  3. Check file permissions on the network configuration script
    Use 'ls -la' or 'stat' command on the network configuration script to view its permission bits. Look for 'w' permissions in the 'other' field (e.g., permissions like 777 or any permission string showing 'rw-rw-rw-')
    Affected if The script has world-writable permissions (octal 777 or similar, where the third digit contains '7' or '6' for write access)
  4. Verify write access for non-privileged users
    As a standard authenticated (non-admin) user, attempt to echo or redirect content to the network configuration script path to confirm write access is possible
    Affected if Non-privileged users can successfully modify the network configuration script

If the Elspec G5 firmware is version 1.1.4.15 or prior (or below 1.2.1.12) AND the network configuration script has world-writable permissions, the device is vulnerable to privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2.1.12 or later
Fixed in 1.2.1.12
Interim mitigation

Restrict write permissions on the network configuration script to only authorized administrators (e.g., chmod 755 or chown root:root with appropriate group ownership), and upgrade to a patched version if available from the vendor.

Recommended fix High confidence

G5dfr Firmware version 1.2.1.12 or later

  1. Contact Elspec (www.elspec-ltd.com) to obtain the fixed firmware version 1.2.1.12 or later for the G5 digital fault recorder
  2. Review the official firmware upgrade documentation provided by Elspec for the G5dfr device
  3. Ensure you have a backup of the current configuration before proceeding with the firmware update
  4. Apply the firmware upgrade following the vendor's recommended procedure, typically via the device's web interface or dedicated upgrade tool
  5. After upgrade, verify that the network configuration script permissions have been corrected (no longer world-writable)
  6. Confirm normal device operation and that privilege escalation is no longer possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in G5dfr Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22078 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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