GHSA-jmp2-wc4p-wfh2

Suggest an improvement
Source
https://github.com/advisories/GHSA-jmp2-wc4p-wfh2
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/05/GHSA-jmp2-wc4p-wfh2/GHSA-jmp2-wc4p-wfh2.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-jmp2-wc4p-wfh2
Aliases
Related
Published
2023-05-05T02:25:00Z
Modified
2024-08-20T20:58:43.745045Z
Severity
  • 3.0 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N CVSS Calculator
Summary
Mutagen list and monitor operations do not neutralize control characters in text controlled by remote endpoints
Details

Impact

Mutagen command line operations, as well as the log output from mutagen daemon run, are susceptible to control characters that could be provided by remote endpoints. This can cause terminal corruption, either intentional or unintentional, if these characters are present in error messages, file paths/names, and/or log output. This could be used as an attack vector if synchronizing with an untrusted remote endpoint, synchronizing files not under control of the user, or forwarding to/from an untrusted remote endpoint. On very old systems with terminals susceptible to issues such as CVE-2003-0069, the issue could theoretically cause code execution.

Patches

The problem has been patched in Mutagen v0.16.6 and v0.17.1. Earlier versions of Mutagen are no longer supported and will not be patched. Versions of Mutagen after v0.18.0 will also have the patch merged.

One caveat is that the templating functionality of Mutagen's list and monitor commands has been only partially patched. In particular, the json template function already provided escaping and no patching was necessary. However, raw template output has been left unescaped because this raw output may be necessary for commands which embed Mutagen. To aid these commands, a new shellSanitize template function has been added which provides control character neutralization in strings.

Workarounds

Avoiding synchronization of untrusted files or interaction with untrusted remote endpoints should mitigate any risk.

References

A similar issue can be seen in kubernetes/kubernetes#101695.

Database specific
{
    "github_reviewed_at": "2023-05-05T02:25:00Z",
    "cwe_ids": [
        "CWE-116",
        "CWE-150"
    ],
    "nvd_published_at": "2023-05-08T18:15:14Z",
    "severity": "LOW",
    "github_reviewed": true
}
References

Affected packages

Go / github.com/mutagen-io/mutagen

Package

Name
github.com/mutagen-io/mutagen
View open source insights on deps.dev
Purl
pkg:golang/github.com/mutagen-io/mutagen

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.16.6

Go / github.com/mutagen-io/mutagen-compose

Package

Name
github.com/mutagen-io/mutagen-compose
View open source insights on deps.dev
Purl
pkg:golang/github.com/mutagen-io/mutagen-compose

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.17.1

Go / github.com/mutagen-io/mutagen

Package

Name
github.com/mutagen-io/mutagen
View open source insights on deps.dev
Purl
pkg:golang/github.com/mutagen-io/mutagen

Affected ranges

Type
SEMVER
Events
Introduced
0.17.0
Fixed
0.17.1