Update: simplified server.json, updating other files for next release #209
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Quadratic complexity when checking name constraints in crypto/x509 Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Parsing DER payload can cause memory exhaustion in encoding/asn1 Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
ALPN negotiation error contains attacker controlled information in crypto/tls Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Unbounded allocation when parsing GNU sparse map in archive/tar Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Quadratic complexity when parsing some invalid inputs in encoding/pem Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Excessive CPU consumption in ParseAddress in net/mail Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Lack of limit when parsing cookies can cause memory exhaustion in net/http Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Insufficient validation of bracketed IPv6 hostnames in net/url Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Excessive CPU consumption in Reader.ReadResponse in net/textproto Warning
| @@ -1 +1 @@ | |||
| 1.24.7 | |||
| 1.25.1 | |||
Check warning
Code scanning / Go Stdlib Scanner
Panic when validating certificates with DSA public keys in crypto/x509 Warning
2 participants
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.