G5dfr FirmwareOperating system · Elspec Ltd

CVE-2024-22079

HIGH · 7.5 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 1.2.1.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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. Directory traversal can occur via the system logs download mechanism.

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 confidence

A directory traversal vulnerability in the Elspec G5 digital fault recorder allows attackers to access arbitrary files on the system through the system logs download mechanism by manipulating path traversal sequences in the request.

MitigationApply the vendor firmware update to version 1.1.4.15+ when available. If no patch exists, restrict network access to the device's management interface and implement input validation on file download parameters.

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

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

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

  1. Identify device model
    Confirm the target system is an Elspec G5 digital fault recorder (G5dfr) by checking system information, device labeling, or management interface
    Affected if Device is not an Elspec G5dfr unit - not affected by this specific CVE
  2. Check firmware version
    Access the device management interface or use vendor diagnostic commands to retrieve the installed firmware version, then compare against the affected range of < 1.2.1.12
    Affected if Firmware version is lower than 1.2.1.12 - device is vulnerable if the logs download feature is accessible
  3. Verify logs download feature availability
    Determine whether the system logs download functionality is enabled and accessible on the device - this may be via web interface, API endpoint, or management service
    Affected if The logs download mechanism is exposed and accessible to the attacker
  4. Assess network exposure
    Check if the device management interface or logs download service is accessible from untrusted networks or the internet
    Affected if The logs download feature is reachable from network segments that do not require authentication or are untrusted
  5. Review access controls
    Inspect the device or network configuration for authentication requirements on the logs download endpoint and any input validation on path parameters
    Affected if No authentication is required or path traversal input is not validated before processing requests

The environment is affected if the device is an Elspec G5dfr running firmware below version 1.2.1.12 AND the logs download feature is accessible to an attacker without proper input validation on path parameters.

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

Apply the vendor firmware update to version 1.1.4.15+ when available. If no patch exists, restrict network access to the device's management interface and implement input validation on file download parameters.

Recommended fix Moderate confidence

G5dfr Firmware 1.2.1.12 or later

  1. 1. Contact Elspec technical support or visit the official Elspec website (www.elspec-ltd.com) to obtain the firmware version 1.2.1.12 or later.
  2. 2. Backup the current G5 device configuration before upgrading.
  3. 3. Upload the firmware update through the device's admin interface using the proper firmware update mechanism.
  4. 4. After upgrade, verify the device is running version 1.2.1.12 or later.
  5. 5. Test that the system logs download functionality works correctly and the directory traversal vulnerability is resolved.

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

Fix this in G5dfr Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22079 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22079 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