CVE-2023-24531
Output of "go env" does not sanitize values in cmd/go
Published: Jul 2, 2024Updated: Mar 28, 2025 Sources: CVE List NVD BDU
Description
Command go env is documented as outputting a shell script containing the Go environment. However, go env doesn't sanitize values, so executing its output as a shell script can cause various bad bahaviors, including executing arbitrary commands or inserting new environment variables. This issue is relatively minor because, in general, if an attacker can set arbitrary environment variables on a system, they have better attack vectors than making "go env" print them out.
No summary for this CVE yet.
CVSS Vector Breakdown
Exploitability
AV:NAttack VectorNetwork
AC:LAttack ComplexityLow
PR:NPrivileges RequiredNone
UI:NUser InteractionNone
Scope
S:UScopeUnchanged
Impact
C:HConfidentialityHigh
I:HIntegrityHigh
A:HAvailabilityHigh
Affected Products
Go toolchain
oss-project·USaka golang, cmd/go, go compiler toolchain
cmd/goLibrary
OSS Libraries / goCanonical Ltd.
commercial·GBaka canonical
Сообщество свободного программного обеспечения
oss-projectaka fsf
ООО «Ред Софт»
commercial·RUaka red soft
The Go Project
oss-projectaka golang-google-protobuf, crypto, go
Exploitability
Official Patch Available
References
and 10 more references View all →
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2023-24531 and every CVE in our database. Create a free account — no credit card required.
Create Free AccountPlain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows