CVE-2024-0674
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 · uneditedPrivilege escalation vulnerability in Lamassu Bitcoin ATM Douro machines, in its 7.1 version, which could allow a local user to acquire root permissions by modifying the updatescript.js, inserting special code inside the script and creating the done.txt file. This would cause the watchdog process to run as root and execute the payload stored in the updatescript.js.
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 confidenceLocal privilege escalation in Lamassu Bitcoin ATM Douro v7.1 where an authenticated local user can modify updatescript.js to inject malicious code and create done.txt, causing the watchdog process to execute the payload with root 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= 7.1= 7.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.
-
Verify firmware version is 7.1Check system information or firmware version file on the Lamassu device. Common locations include /etc/version, /proc/version, or the device management interface.Affected if The installed firmware version is exactly 7.1 or falls within the 7.1.x branch for Lamassu Douro or Douro II.
-
Locate updatescript.js fileSearch for updatescript.js in the system, typically found in the update or firmware directory. Common paths may include /opt/lamassu/updates/ or similar application directories.Affected if The updatescript.js file exists on the system.
-
Check file permissions on updatescript.jsUse 'ls -la <path>/updatescript.js' to inspect owner, group, and permission bits. Verify if writable by non-root users.Affected if updatescript.js is writable by users other than root or the application service account.
-
Check for presence of done.txt trigger fileLook for done.txt in the directory where updatescript.js resides or in watchdog-monitored directories. Use 'find / -name done.txt 2>/dev/null'.Affected if done.txt exists in a directory monitored by the watchdog process.
-
Verify watchdog process is activeCheck if the watchdog process is running using 'ps aux | grep -i watch' or 'systemctl status watchdog' if applicable.Affected if The watchdog process is running and monitors the update directory.
You are affected if the firmware is version 7.1 AND updatescript.js is writable by non-privileged users AND the watchdog process is active, allowing a local authenticated user to inject code that executes with root privileges.
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 dataRestrict file permissions on updatescript.js to prevent unauthorized modification, implement code signing verification for update scripts, and ensure the watchdog process validates script integrity and user authorization before execution.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0674 — 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-0674 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