CVE-2025-4673 found in golang/stdlib@v1.24.0

CVE-2025-4673 found in golang/stdlib@v1.24.0

Important

Risk: 3.10 (Low) CVSS: 6.8

Description

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.

Affected component

The vulnerability is in pkg:golang/stdlib@v1.24.0, found in artifacts pkg:devguard/bizzareorganization/jojoasset/adventurerepo.

Recommended fix

Upgrade to version v1.24.4 or later.

# Update all golang packages
go get -u ./... 
# Update only this package
go get stdlib@v1.24.4 

Additional guidance for mitigating vulnerabilities

Visit our guides on devguard.org

See more details...

Path to component

 %%{init: { 'theme':'base', 'themeVariables': {
'primaryColor': '#F3F3F3',
'primaryTextColor': '#0D1117',
'primaryBorderColor': '#999999',
'lineColor': '#999999',
'secondaryColor': '#ffffff',
'tertiaryColor': '#ffffff'
} }}%%
 flowchart TD
root(["root"]) --- stdlib(["stdlib"])

classDef default stroke-width:2px
Risk Factor Value Description
Vulnerability Depth 0 The vulnerability is in a direct dependency of your project.
EPSS 0.01 % The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
EXPLOIT Not available We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database. There are no script kiddies exploiting this vulnerability.
CVSS-BE 6.8 - Exploiting this vulnerability significantly impacts confidentiality.
CVSS-B 6.8 - The vulnerability can be exploited over the network without needing physical access.
- It is difficult for an attacker to exploit this vulnerability and may require special conditions.
- An attacker does not need any special privileges or access rights.
- No user interaction is needed for the attacker to exploit this vulnerability.
- The vulnerability can affect other systems as well, not just the initial system.
- There is a high impact on the confidentiality of the information.

More details can be found in DevGuard


Interact with this vulnerability

You can use the following slash commands to interact with this vulnerability:

👍 Reply with this to acknowledge and accept the identified risk.

/accept I accept the risk of this vulnerability, because ...

⚠️ Mark the risk as false positive: Use one of these commands if you believe the reported vulnerability is not actually a valid issue.

/component-not-present The vulnerable component is not included in the artifact.
/vulnerable-code-not-present The component is present, but the vulnerable code is not included or compiled.
/vulnerable-code-not-in-execute-path The vulnerable code exists, but is never executed at runtime.
/vulnerable-code-cannot-be-controlled-by-adversary Built-in protections prevent exploitation of this vulnerability.
/inline-mitigations-already-exist The vulnerable code cannot be controlled or influenced by an attacker.

🔁 Reopen the risk: Use this command to reopen a previously closed or accepted vulnerability.

/reopen ...