quic-go to 0.40.1 #4872

New issue

Closed

opened 2026-05-05 14:50:20 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 14:50:20 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fatedier/frp/pull/3962
Author: @chncaption
Created: 1/31/2024
Status: ❌ Closed

Base: dev ← Head: oscs_fix_cmst0k0au51oj0c3u33g

📝 Commits (1)

b4a6269 update github.com/quic-go/quic-go v0.37.4 to 0.40.1

📊 Changes

2 files changed (+12 additions, -3 deletions)

View changed files

📝 go.mod (+4 -3)
📝 go.sum (+8 -0)

📄 Description

What happened？

There are 1 security vulnerabilities found in github.com/quic-go/quic-go v0.37.4

CVE-2023-49295

What did I do？

Upgrade github.com/quic-go/quic-go from v0.37.4 to 0.40.1 for vulnerability fix

What did you expect to happen？

Ideally, no insecure libs should be used.

How can we automate the detection of these types of issues?

By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.

The specification of the pull request

PR Specification from OSCS

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fatedier/frp/pull/3962 **Author:** [@chncaption](https://github.com/chncaption) **Created:** 1/31/2024 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `oscs_fix_cmst0k0au51oj0c3u33g` --- ### 📝 Commits (1) - [`b4a6269`](https://github.com/fatedier/frp/commit/b4a6269b42ebb767d348d2c989373f072973ffc2) update github.com/quic-go/quic-go v0.37.4 to 0.40.1 ### 📊 Changes **2 files changed** (+12 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+4 -3) 📝 `go.sum` (+8 -0) </details> ### 📄 Description ### What happened？ There are 1 security vulnerabilities found in github.com/quic-go/quic-go v0.37.4 - [CVE-2023-49295](https://www.oscs1024.com/hd/CVE-2023-49295) ### What did I do？ Upgrade github.com/quic-go/quic-go from v0.37.4 to 0.40.1 for vulnerability fix ### What did you expect to happen？ Ideally, no insecure libs should be used. ### How can we automate the detection of these types of issues? By using the [GitHub Actions](https://github.com/murphysecurity/actions) configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline. ### The specification of the pull request [PR Specification](https://www.oscs1024.com/docs/pr-specification/) from OSCS --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>