dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-1491

HIGH · 7.5 CVSS v3.1 Published 2024-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The devices allow access to an unprotected endpoint that allows MPFS file system binary image upload without authentication. The MPFS2 file system module provides a light-weight read-only file system that can be stored in external EEPROM, external serial flash, or internal flash program memory. This file system serves as the basis for the HTTP2 web server module, but is also used by the SNMP module and is available to other applications that require basic read-only storage capabilities. This can be exploited to overwrite the flash program memory that holds the web server's main interfaces and execute arbitrary code.

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

Devices have an unprotected endpoint allowing unauthenticated upload of MPFS2 file system binary images. MPFS2 is a read-only file system stored in external EEPROM, serial flash, or internal flash memory, used by the HTTP2 web server and SNMP modules. Successful exploitation overwrites flash program memory containing web server interfaces, enabling arbitrary code execution.

MitigationImplement authentication and authorization checks on the file system upload endpoint, and consider adding flash memory write protection or cryptographic signing of firmware images to prevent unauthorized modifications.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 if HTTP2 web server is enabled
    Review device configuration or web server settings to determine if the HTTP2 module is active. Check device documentation or web interface for enabled protocols.
    Affected if HTTP2 web server is enabled and the device accepts MPFS2 file system uploads
  2. Verify if the file system upload endpoint lacks authentication
    Attempt to access the MPFS2 upload endpoint (commonly paths like /mpfs/upload, /fs/upload, or firmware update interfaces) without providing credentials. If the endpoint responds without requiring login, it is unprotected.
    Affected if The upload endpoint accepts requests without authentication credentials
  3. Determine if SNMP module is in use
    Check device configuration for SNMP settings. SNMP uses MPFS2 for read-only file system storage, making it a potential attack vector.
    Affected if SNMP is enabled and the device allows network-based file system management
  4. Compare installed firmware version against vendor release notes
    Locate the firmware version through device web interface, CLI (show version), or SNMP. Review vendor security advisories for CVE-2024-1491 to identify if your version falls within affected releases.
    Affected if Firmware version matches or predates versions listed as vulnerable to this CVE
  5. Check for exposed upload interfaces on network
    Scan device network services for HTTP/HTTPS endpoints that handle file system or firmware uploads. Review any API endpoints related to MPFS2 or filesystem management.
    Affected if Upload endpoints are reachable from network without access control restrictions

A device is affected if it runs a vulnerable firmware version, has HTTP2 web server enabled, and exposes an unauthenticated MPFS2 file system upload endpoint accessible over the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authentication and authorization checks on the file system upload endpoint, and consider adding flash memory write protection or cryptographic signing of firmware images to prevent unauthorized modifications.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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