Skip to content

Improper Neutralization of Special Elements used in a Command ('Command Injection') in Weblate

High severity GitHub Reviewed Published Mar 4, 2022 in WeblateOrg/weblate • Updated Feb 3, 2023

Package

pip Weblate (pip)

Affected versions

< 4.11.1

Patched versions

4.11.1

Description

Impact

Weblate didn't correctly sanitize some arguments passed to Git and Mercurial, which allowed changing their behavior in an unintended way.

Patches

The issues were fixed in the 4.11.1 release. The following commits are addressing it:

  • 35d59f1f040541c358cece0a8d4a63183ca919b8
  • d83672a3e7415da1490334e2c9431e5da1966842

Workarounds

Instances in which untrusted users cannot create new components are not affected.

References

For more information

If you have any questions or comments about this advisory:

References

@nijel nijel published to WeblateOrg/weblate Mar 4, 2022
Published by the National Vulnerability Database Mar 4, 2022
Published to the GitHub Advisory Database Mar 4, 2022
Reviewed Mar 4, 2022
Last updated Feb 3, 2023

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
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.294%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-23915

GHSA ID

GHSA-3872-f48p-pxqj

Source code

Credits

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