dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-37019

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Northern.tech Mender Enterprise before 3.6.4 and 3.7.x before 3.7.4 has Weak Authentication.

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

Mender Enterprise versions before 3.6.4 and 3.7.x before 3.7.4 contain weak authentication that could allow unauthorized access to the platform with critical severity (CVSS 9.8).

MitigationUpgrade Mender Enterprise to version 3.6.4, 3.7.4, or later to resolve the weak authentication vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Mender Enterprise is installed
    Check for Mender processes running on the system (e.g., 'ps aux | grep mender') or look for Mender installation directories
    Affected if Mender Enterprise process or installation is found on the system
  2. Determine the installed Mender Enterprise version
    Run 'mender --version' or check version information in the Mender installation directory (/usr/share/mender/ or similar), or inspect the mender-server deployment manifests
    Affected if Version cannot be determined or is below 3.6.4 or in the 3.7.0-3.7.3 range
  3. Compare version against affected ranges
    Compare your installed version number to the affected ranges: versions before 3.6.4, or 3.7.0 through 3.7.3
    Affected if Installed version is 3.7.3 or earlier (but not 3.6.4 or later), or is any version before 3.6.4
  4. Confirm authentication is enabled
    Verify that Mender Enterprise user authentication is configured and active (check user database, API endpoints responding to auth requests)
    Affected if Mender Enterprise authentication module is in use (likely always true for Enterprise installations)

If Mender Enterprise is installed and the version is below 3.6.4 or between 3.7.0 and 3.7.3, the environment is affected by this weak authentication vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mender Enterprise to version 3.6.4, 3.7.4, or later to resolve the weak authentication vulnerability.

Recommended fix High confidence

Mender Enterprise 3.6.4+ or 3.7.4+

  1. Backup your Mender Enterprise installation and database before proceeding
  2. Identify your current Mender Enterprise version using the Mender UI or API
  3. Upgrade Mender Enterprise to version 3.6.4 or later if running 3.6.x
  4. Upgrade Mender Enterprise to version 3.7.4 or later if running 3.7.x
  5. After upgrade, verify authentication is functioning correctly and review access logs

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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