Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
azure/azure-sdk-for-go
main @ 488a35f
24
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Information Disclosure: 7 prior fixes. Scrutinize any change in this area.
sdk/azcore/runtime: most-fixed (5 issues). Treat as high-risk during review.
6 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Command Injection: AzureCLICredential was vulnerable to command injection on Windows because it passed unsanitized arguments to cmd.exe via exec.CommandContext. Developers must avoid direct string interpolation or unsafe shell wrappers, using explicit argument passing and SysProcAttr.CmdLine formatting instead.
Information Disclosure: Logging and distributed tracing pipelines historically leaked sensitive query parameters, custom headers, and token context details in plaintext. Strict allowlist validation and explicit slice allocation are required when constructing diagnostic wrappers.
SSRF: The authentication challenge policy was vulnerable to credential theft via SSRF because it did not verify that the resource in the WWW-Authenticate challenge matched the requested domain, risking token leakage to malicious hosts.