Skip to content

Commit

Permalink
update badge 20250129/070808
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored Jan 29, 2025
1 parent 537139a commit 5ef6a33
Showing 1 changed file with 74 additions and 0 deletions.
74 changes: 74 additions & 0 deletions .github/sec-lite.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,77 @@
- https://www.cve.org/CVERecord?id=CVE-2024-45338
PublishedDate: '2024-12-18T21:15:08.173Z'
LastModifiedDate: '2024-12-31T20:16:06.603Z'
- VulnerabilityID: CVE-2024-45336
PkgID: [email protected]
PkgName: stdlib
PkgIdentifier:
PURL: pkg:golang/[email protected]
UID: c32ee6844a95cf7d
InstalledVersion: v1.23.3
FixedVersion: 1.22.11, 1.23.5, 1.24.0-rc2
Status: fixed
Layer:
Digest: sha256:1f383918363ac911be51cac15c9dff19f16778bfed1ab9f3e1b9200fb8868c96
DiffID: sha256:ac8c4e6ab28289487a8db7966647ea46d388098db92d5174c650c9c25b560436
PrimaryURL: https://avd.aquasec.com/nvd/cve-2024-45336
DataSource:
ID: govulndb
Name: The Go Vulnerability Database
URL: https://pkg.go.dev/vuln/
Title: 'golang: net/http: net/http: sensitive headers incorrectly sent after cross-domain redirect'
Description: The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
Severity: MEDIUM
VendorSeverity:
redhat: 2
CVSS:
redhat:
V3Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
V3Score: 5.9
References:
- https://access.redhat.com/security/cve/CVE-2024-45336
- https://go.dev/cl/643100
- https://go.dev/issue/70530
- https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ
- https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ
- https://nvd.nist.gov/vuln/detail/CVE-2024-45336
- https://pkg.go.dev/vuln/GO-2025-3420
- https://www.cve.org/CVERecord?id=CVE-2024-45336
PublishedDate: '2025-01-28T02:15:28.807Z'
LastModifiedDate: '2025-01-28T16:15:38.22Z'
- VulnerabilityID: CVE-2024-45341
PkgID: [email protected]
PkgName: stdlib
PkgIdentifier:
PURL: pkg:golang/[email protected]
UID: c32ee6844a95cf7d
InstalledVersion: v1.23.3
FixedVersion: 1.22.11, 1.23.5, 1.24.0-rc2
Status: fixed
Layer:
Digest: sha256:1f383918363ac911be51cac15c9dff19f16778bfed1ab9f3e1b9200fb8868c96
DiffID: sha256:ac8c4e6ab28289487a8db7966647ea46d388098db92d5174c650c9c25b560436
PrimaryURL: https://avd.aquasec.com/nvd/cve-2024-45341
DataSource:
ID: govulndb
Name: The Go Vulnerability Database
URL: https://pkg.go.dev/vuln/
Title: 'golang: crypto/x509: crypto/x509: usage of IPv6 zone IDs can bypass URI name constraints'
Description: A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain. Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs.
Severity: MEDIUM
VendorSeverity:
redhat: 1
CVSS:
redhat:
V3Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
V3Score: 4.2
References:
- https://access.redhat.com/security/cve/CVE-2024-45341
- https://go.dev/cl/643099
- https://go.dev/issue/71156
- https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ
- https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ
- https://nvd.nist.gov/vuln/detail/CVE-2024-45341
- https://pkg.go.dev/vuln/GO-2025-3373
- https://www.cve.org/CVERecord?id=CVE-2024-45341
PublishedDate: '2025-01-28T02:15:29.147Z'
LastModifiedDate: '2025-01-28T16:15:38.65Z'

0 comments on commit 5ef6a33

Please sign in to comment.