Security readout for executives and security teams
Plain-English summary
This issue affects Go programs on Windows that use the standard os/exec package in an unsafe edge case. A local attacker who can influence the working directory may cause the program to run an unintended local binary, leading to full confidentiality, integrity, and availability impact in that process context.
Executive priority
Treat as a high-priority engineering remediation for Windows Go workloads, especially privileged services. Urgency is below emergency patching because sources do not show active exploitation, but affected binaries should be rebuilt during the next controlled release window.
Technical view
Before Go 1.17.11 and 1.18.3, os/exec Cmd.Start could execute an unintended binary from the working directory when Cmd.Path was unset and Run, Start, Output, or CombinedOutput was called on Windows. The CVE is scored CVSS 7.8 with local, low-complexity, low-privilege prerequisites.
Likely exposure
Exposure is most likely in Windows-hosted Go applications built with affected Go releases and using os/exec with Cmd.Path unset. Risk rises where an attacker can write to or control the process working directory. Non-Windows deployments are not indicated by the provided sources.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not state active exploitation. The attack requires local access or equivalent ability to place a file in the relevant working directory, but successful abuse could run code with the vulnerable process privileges.
Researcher notes
Focus review on Windows os/exec call sites and process working-directory control. The Go issue, change list, commit, announcement, and GO-2022-0532 entry consistently identify the vulnerable behavior and fixed release lines. Evidence is sufficient for affected-version and remediation direction.
Mitigation direction
- Upgrade Go toolchains to 1.17.11, 1.18.3, or later supported releases.
- Rebuild and redeploy Windows Go binaries built with affected Go versions.
- Audit os/exec usage where Cmd.Path may be unset.
- Restrict write access to service and application working directories.
- Check official Go guidance for any application-specific follow-up.
Validation and detection
- Inventory Go versions used to build Windows applications and services.
- Identify applications calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput.
- Review code paths where Cmd.Path may be empty or implicitly derived.
- Verify service working directories are not attacker-writable.
- Confirm rebuilt binaries use a fixed Go release.
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 lookupCVE-2022-30580 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://go.dev/cl/403759CVE reference
- https://go.googlesource.com/go/+/960ffa98ce73ef2c2060c84c7ac28d37a83f345eCVE reference
- https://go.dev/issue/52574CVE reference
- https://groups.google.com/g/golang-announce/c/TzIC9-t8Ytg/m/IWz5T6x7AAAJCVE reference
- https://pkg.go.dev/vuln/GO-2022-0532CVE 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.