Allocation of Resources Without Limits or Throttling Affecting go1.18-doc package, versions <1.18.7-150000.1.34.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating

    Threat Intelligence

    EPSS
    0.21% (59th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-SLES154-GO118DOC-3057238
  • published 20 Oct 2022
  • disclosed 19 Oct 2022

How to fix?

Upgrade SLES:15.4 go1.18-doc to version 1.18.7-150000.1.34.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream go1.18-doc package and not the go1.18-doc package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

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.

CVSS Scores

version 3.1
Expand this section

NVD

7.5 high
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    None
  • Integrity (I)
    None
  • Availability (A)
    High
Expand this section

SUSE

7.5 high
Expand this section

Red Hat

6.5 medium