Bugs fixes in "golang-1.22"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2024-34158 | Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-34156 | Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-202 | 2024-10-23 |
| CVE | CVE-2024-34155 | Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-24791 | The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational | 2024-10-23 |
| CVE | CVE-2024-34158 | Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-34156 | Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-202 | 2024-10-23 |
| CVE | CVE-2024-34155 | Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-24791 | The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational | 2024-10-23 |
| CVE | CVE-2024-34158 | Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-34156 | Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-202 | 2024-10-23 |
| CVE | CVE-2024-34155 | Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-24791 | The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational | 2024-10-23 |
| CVE | CVE-2024-34158 | Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-34156 | Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-202 | 2024-10-23 |
| CVE | CVE-2024-34155 | Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-24791 | The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational | 2024-10-23 |
| CVE | CVE-2024-34158 | Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-34156 | Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-202 | 2024-10-23 |
| CVE | CVE-2024-34155 | Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. | 2024-10-23 |
| CVE | CVE-2024-24791 | The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational | 2024-10-23 |
About
-
Send Feedback to @ubuntu_updates
