Skip to content

MongoDB Shell may be susceptible to Control Character Injection via autocomplete

High severity GitHub Reviewed Published Feb 27, 2025 to the GitHub Advisory Database • Updated Feb 27, 2025

Package

npm mongosh (npm)

Affected versions

< 2.3.9

Patched versions

2.3.9

Description

The MongoDB Shell may be susceptible to control character injection where an attacker with control of the mongosh autocomplete feature, can use the autocompletion feature to input and run obfuscated malicious text. This requires user interaction in the form of the user using ‘tab’ to autocomplete text that is a prefix of the attacker’s prepared autocompletion. This issue affects mongosh versions prior to 2.3.9. 

The vulnerability is exploitable only when mongosh is connected to a cluster that is partially or fully controlled by an attacker.

References

Published by the National Vulnerability Database Feb 27, 2025
Published to the GitHub Advisory Database Feb 27, 2025
Reviewed Feb 27, 2025
Last updated Feb 27, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-1691

GHSA ID

GHSA-43g5-2wr2-q7vj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.