Security readout for executives and security teams
Plain-English summary
This vulnerability affects older Go toolchains during software builds, not running Go applications directly. A malicious linked object file processed through cgo could make the Go build tools execute arbitrary code. The main business risk is compromise of developer machines or CI systems that build untrusted or tampered code.
Executive priority
Prioritize remediation where Go builds are part of production release, CI, or third-party code intake. This is a build-chain compromise risk rather than a broad internet-facing runtime flaw, so urgency depends on how much untrusted code enters your build process.
Technical view
Before Go 1.14.12 and Go 1.15.5, cmd/go and cmd/cgo mishandled an unquoted symbol name from a linked object file. With cgo involved, that symbol name could inject code executed at build time. The issue is classified as CWE-94, but the source bundle provides no CVSS score.
Likely exposure
Exposure is most likely in CI, build servers, developer workstations, or release pipelines using vulnerable Go versions with cgo and linked object files. Systems only running already-built Go binaries are not the primary exposure described by the sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Abuse appears to require a malicious linked object file reaching a vulnerable Go build process using cgo, making supply-chain and untrusted-source build scenarios the main concern.
Researcher notes
Key unknowns are CVSS severity and observed exploitation. Validation should focus on vulnerable toolchain versions, cgo usage, and whether linked object files can be influenced by dependencies or external contributors. Avoid assuming application runtime exposure without evidence from the build path.
Mitigation direction
- Upgrade Go toolchains to 1.14.12, 1.15.5, or a later fixed release.
- Remove vulnerable Go versions from CI images and developer build environments.
- Review vendor Go guidance before relying on workarounds.
- Restrict builds that consume untrusted object files or cgo inputs.
- Pin and verify Go toolchain versions in release pipelines.
Validation and detection
- Inventory Go versions on CI agents, build containers, and developer images.
- Identify projects using cgo or linked object files.
- Confirm vulnerable Go versions before 1.14.12 or 1.15.5 are retired.
- Review build provenance for untrusted native objects.
- Check Go advisory references for any environment-specific guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-28366 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://go.dev/cl/269658CVE reference
- https://go.googlesource.com/go/+/062e0e5ce6df339dc26732438ad771f73dbf2292CVE reference
- https://go.dev/issue/42559CVE reference
- https://groups.google.com/g/golang-announce/c/NpBGTTmKzpMCVE reference
- https://pkg.go.dev/vuln/GO-2022-0475CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.