[Eclipse Mosquito] Double free vulnerability in Mosquitto

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.

Basic information

Project name: Eclipse Mosquitto

Project id: iot.mosquitto

Request type: publication

Versions affected: [2.0.0, 2.0.18]

Common Weakness Enumeration:

• {CWE-415: Double Free}

Common Vulnerability Scoring System: {CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N}

Summary:

In Eclipse Mosquito, versions from 2.0.0 through 2.0.18, if a Mosquitto broker is configured to create an outgoing bridge connection, and that bridge connection has an incoming topic configured that makes use of topic remapping, then if the remote connection sends a crafted PUBLISH packet to the broker a double free will occur with a subsequent crash of the broker.

Credits: song xiangpu

Links:

• vulnerability-reports#197 (closed)
• https://github.com/eclipse-mosquitto/mosquitto/releases/tag/v2.0.19
• https://mosquitto.org/

Tracking

This section will completed by the project team.

• Reserve an entry only
• We're ready for this issue to be reported to the central authority (i.e., make this public now)
• (when applicable) The GitHub Security Advisory is ready to be published now

Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.

This section will be completed by the EMO.

CVE: {cve}

• All required information is provided
• CVE Assigned
• Pushed to Mitre
• Accepted by Mitre

assigned to @mbarbero and @mrybczyn

We are going to use CVE-2024-3935 for this issue.

added cvereserved label

marked this issue as related to vulnerability-reports#197 (closed)

I prepared the following CVE entry:

The CVE has been published, removing confidentiality from the ticket.

removed cvereserved label

added cvepublished label

made the issue visible to everyone

closed