Количество 43
Количество 43

CVE-2022-2880
CVE-2022-2880
Requests forwarded by ReverseProxy include the raw query parameters fr ...
ELSA-2023-2357
ELSA-2023-2357: git-lfs security and bug fix update (MODERATE)
GHSA-m3hq-grv6-h853
Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparseable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparseable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

CVE-2022-2879
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

CVE-2022-2879
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

CVE-2022-2879
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

CVE-2022-2879
CVE-2022-2879
Reader.Read does not set a limit on the maximum size of file headers. ...

CVE-2022-41715
Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

CVE-2022-41715
Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

CVE-2022-41715
Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

CVE-2022-41715
CVE-2022-41715
Programs which compile regular expressions from untrusted sources may ...
GHSA-fqpx-62jv-7r6r
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.
GHSA-5wvm-rxcf-6cg8
Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.
ELSA-2023-2592
ELSA-2023-2592: golang-github-cpuguy83-md2man security, bug fix, and enhancement update (MODERATE)

SUSE-SU-2023:2182-1
Security update for SUSE Manager Client Tools

SUSE-SU-2023:2598-1
Security update for golang-github-prometheus-prometheus

SUSE-SU-2024:3288-1
Security update for golang-github-prometheus-prometheus
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-2880 Requests forwarded by ReverseProxy include the raw query parameters fr ... | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
ELSA-2023-2357 ELSA-2023-2357: git-lfs security and bug fix update (MODERATE) | около 2 лет назад | |||
GHSA-m3hq-grv6-h853 Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparseable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparseable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
![]() | CVE-2022-2879 Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад |
![]() | CVE-2022-2879 Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. | CVSS3: 6.5 | 0% Низкий | больше 2 лет назад |
![]() | CVE-2022-2879 Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад |
![]() | CVSS3: 7.5 | 0% Низкий | 10 месяцев назад | |
CVE-2022-2879 Reader.Read does not set a limit on the maximum size of file headers. ... | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
![]() | CVE-2022-41715 Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад |
![]() | CVE-2022-41715 Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected. | CVSS3: 6.5 | 0% Низкий | больше 2 лет назад |
![]() | CVE-2022-41715 Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад |
![]() | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-41715 Programs which compile regular expressions from untrusted sources may ... | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
GHSA-fqpx-62jv-7r6r Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
GHSA-5wvm-rxcf-6cg8 Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected. | CVSS3: 7.5 | 0% Низкий | больше 2 лет назад | |
ELSA-2023-2592 ELSA-2023-2592: golang-github-cpuguy83-md2man security, bug fix, and enhancement update (MODERATE) | около 2 лет назад | |||
![]() | SUSE-SU-2023:2182-1 Security update for SUSE Manager Client Tools | около 2 лет назад | ||
![]() | SUSE-SU-2023:2598-1 Security update for golang-github-prometheus-prometheus | почти 2 года назад | ||
![]() | SUSE-SU-2024:3288-1 Security update for golang-github-prometheus-prometheus | 9 месяцев назад |
Уязвимостей на страницу