You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the (8f89e12) patch does not contain the affected components client/cache/file.go and core/logs/alils/request.go.
According to the details.pdf in GHSA-6g9p-wv47-4fxq, CVE-2024-40465 is more of an "md5 is insecure" issue. And it still uses md5.
I'm a little confused, please help confirm whether the CVE-2024-40465 vulnerability has been fixed in beego v2.2.1.
What did you expect to see?
Please help confirm whether the CVE-2024-40465 vulnerability has been fixed in beego v2.2.1.
The text was updated successfully, but these errors were encountered:
I see on the nvd website that the CVE-2024-40465 vulnerability has been fixed in beego v2.2.1.
Reference: GHSA-6g9p-wv47-4fxq
However, the (8f89e12) patch does not contain the affected components client/cache/file.go and core/logs/alils/request.go.
According to the details.pdf in GHSA-6g9p-wv47-4fxq, CVE-2024-40465 is more of an "md5 is insecure" issue. And it still uses md5.
I'm a little confused, please help confirm whether the CVE-2024-40465 vulnerability has been fixed in beego v2.2.1.
Please help confirm whether the CVE-2024-40465 vulnerability has been fixed in beego v2.2.1.
The text was updated successfully, but these errors were encountered: