Advisory

GHSA-x5c7-x7m2-rhmf

Also known as: GO-2022-0410

Summary

Local directory executable lookup in sops (Windows-only)

Details

Impact
Windows users using the sops direct editor option (sops file.yaml) can have a local executable named either vi, vim, or nano executed if running sops from cmd.exe

This attack is only viable if an attacker is able to place a malicious binary within the directory you are running sops from. As well, this attack will only work when using cmd.exe or the Windows C library SearchPath function. This is a result of these Windows tools including . within their PATH by default.

If you are using sops within untrusted directories on Windows via `cmd.exe`, please upgrade immediately

As well, if you have `.` within your default $PATH, please upgrade immediately.

More information can be found on the official Go blog: https://blog.golang.org/path-security

Patches
The problem has been resolved in v3.7.1

Now, if Windows users using cmd.exe run into this issue, a warning message will be printed:
vim resolves to executable in current directory (.\vim.exe)

References

  • https://blog.golang.org/path-security

For more information
If you have any questions or comments about this advisory:

  • Open a discussion in sops

Severity

Low Basis: The source's own band: LOW

Dates

Published
2021-05-20 16:50 UTC
Modified
2024-08-21 15:42 UTC

Affected packages and fixes

go.mozilla.org/sops/v3

Go · All systems

Affected

  • introduced 0, fixed 3.7.1 (semver)

Fixed versions

3.7.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences