🛡️ CVE-2018-6574 — toolchain

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Remote command execution via "go get" command with cgo in cmd/go

The "go get" command with cgo is vulnerable to remote command execution by leveraging the gcc or clang plugin feature.

When cgo is enabled, the build step during "go get" invokes the host C compiler, gcc or clang, adding compiler flags specified in the Go source files. Both gcc and clang support a plugin mechanism in which a shared-library plugin is loaded into the compiler, as directed by compiler flags. This means that a Go package repository can contain an attack.so file along with a Go source file that says (for example) "// #cgo CFLAGS: -fplugin=attack.so" causing the attack plugin to be loaded into the host C compiler during the build. Gcc and clang plugins are completely unrestricted in their access to the host system.

Affected software

CVE-2018-6574 is recorded against 1 package.

  • toolchain

Timeline and source

Published on 9 August 2022 and last revised on 20 May 2024. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from OSV.

References

go.googlesource.com (Fix)
go.dev (Report)
groups.google.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2022-08-09
Updated 2026-08-12
Modified 2024-05-20

Affected Packages

Software From version Fixed in
toolchain — —

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2018-6574?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2018-6574 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.