Skip to content
This repository was archived by the owner on May 12, 2025. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
golang.org/x/net v0.23.0 -> v0.38.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-22870

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

CVE-2025-22872

The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse functions, this can result in content following such tags as being placed in the wrong scope during DOM construction, but only when tags are in foreign content (e.g. , , etc contexts).


Non-linear parsing of case-insensitive content in golang.org/x/net/html

CVE-2024-45338 / GHSA-w32m-9786-jp63 / GO-2024-3333

More information

Details

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

CVE-2025-22870 / GHSA-qxp5-gwg8-xv66 / GO-2025-3503

More information

Details

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

CVE-2025-22870 / GHSA-qxp5-gwg8-xv66 / GO-2025-3503

More information

Details

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

Severity

  • CVSS Score: 4.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


golang.org/x/net vulnerable to Cross-site Scripting

CVE-2025-22872 / GHSA-vvgc-356p-c3xw / GO-2025-3595

More information

Details

The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse functions, this can result in content following such tags as being placed in the wrong scope during DOM construction, but only when tags are in foreign content (e.g. , , etc contexts).

Severity

  • CVSS Score: Unknown
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Incorrect Neutralization of Input During Web Page Generation in x/net in golang.org/x/net

CVE-2025-22872 / GHSA-vvgc-356p-c3xw / GO-2025-3595

More information

Details

The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse functions, this can result in content following such tags as being placed in the wrong scope during DOM construction, but only when tags are in foreign content (e.g. , , etc contexts).

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 19, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 4 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.19 -> 1.23.0
golang.org/x/crypto v0.21.0 -> v0.36.0
golang.org/x/sync v0.1.0 -> v0.12.0
golang.org/x/sys v0.18.0 -> v0.31.0
golang.org/x/text v0.14.0 -> v0.23.0

@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.33.0 [security] fix(deps): update module golang.org/x/net to v0.33.0 [security] - autoclosed Jan 9, 2025
@renovate renovate bot closed this Jan 9, 2025
@renovate renovate bot deleted the renovate/go-golang.org-x-net-vulnerability branch January 9, 2025 00:33
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.33.0 [security] - autoclosed fix(deps): update module golang.org/x/net to v0.33.0 [security] Jan 9, 2025
@renovate renovate bot reopened this Jan 9, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 3519bb3 to 0e9c15e Compare January 9, 2025 04:55
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.33.0 [security] fix(deps): update module golang.org/x/net to v0.36.0 [security] Mar 13, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 0e9c15e to 79614e9 Compare March 13, 2025 04:25
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.36.0 [security] fix(deps): update module golang.org/x/net to v0.36.0 [security] - autoclosed Mar 23, 2025
@renovate renovate bot closed this Mar 23, 2025
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.36.0 [security] - autoclosed fix(deps): update module golang.org/x/net to v0.36.0 [security] Mar 23, 2025
@renovate renovate bot reopened this Mar 23, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 438cb71 to 79614e9 Compare March 23, 2025 04:32
@socket-security
Copy link

socket-security bot commented Mar 23, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedgolang.org/​x/​crypto@​v0.21.0 ⏵ v0.36.073 +1100 +75100100100
Updatedgolang.org/​x/​net@​v0.23.0 ⏵ v0.38.075 +1100 +3100100100
Updatedgolang.org/​x/​sync@​v0.1.0 ⏵ v0.12.099100100100100

View full report

@socket-security
Copy link

socket-security bot commented Mar 23, 2025

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert (click for details)
Block Medium
golang.org/x/tools@v0.21.1-0.20240508182429-e35e4ccd0d2d has Native code.

Location: Package overview

From: ?golang/golang.org/x/tools@v0.21.1-0.20240508182429-e35e4ccd0d2d

ℹ Read more on: This package | This alert | Why is native code a concern?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/tools@v0.21.1-0.20240508182429-e35e4ccd0d2d. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 79614e9 to 1c0a295 Compare April 8, 2025 15:05
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.36.0 [security] fix(deps): update module golang.org/x/net to v0.38.0 [security] Apr 17, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 1c0a295 to e528cfc Compare April 17, 2025 01:30
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from e528cfc to e655923 Compare May 7, 2025 10:08
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.38.0 [security] fix(deps): update module golang.org/x/net to v0.38.0 [security] - autoclosed May 9, 2025
@renovate renovate bot closed this May 9, 2025
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.38.0 [security] - autoclosed fix(deps): update module golang.org/x/net to v0.38.0 [security] May 9, 2025
@renovate renovate bot reopened this May 9, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-net-vulnerability branch from 8b2f889 to e655923 Compare May 9, 2025 09:40
@lvpeschke lvpeschke closed this May 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant