Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[20.10] Update go 1.18.7 to address CVE-2022-2879, CVE-2022-2880, CVE-2022-41715 #3800

Merged
merged 1 commit into from Oct 4, 2022

Commits on Oct 4, 2022

  1. [20.10] Update go 1.18.7 to address CVE-2022-2879, CVE-2022-2880, CVE…

    …-2022-41715
    
    From the mailing list:
    
    We have just released Go versions 1.19.2 and 1.18.7, minor point releases.
    
    These minor releases include 3 security fixes following the security policy:
    
    - archive/tar: unbounded memory consumption when reading headers
    
      Reader.Read did 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.
      Reader.Read now limits the maximum size of header blocks to 1 MiB.
    
      Thanks to Adam Korczynski (ADA Logics) and OSS-Fuzz for reporting this issue.
    
      This is CVE-2022-2879 and Go issue https://go.dev/issue/54853.
    
    - net/http/httputil: ReverseProxy should not forward unparseable query parameters
    
      Requests forwarded by ReverseProxy included 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.
    
      ReverseProxy will now sanitize 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.
    
      Thanks to Gal Goldstein (Security Researcher, Oxeye) and
      Daniel Abeles (Head of Research, Oxeye) for reporting this issue.
    
      This is CVE-2022-2880 and Go issue https://go.dev/issue/54663.
    
    - regexp/syntax: limit memory used by parsing regexps
    
      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.
    
      Each regexp being parsed is now limited to a 256 MB memory footprint.
      Regular expressions whose representation would use more space than that
      are now rejected. Normal use of regular expressions is unaffected.
    
      Thanks to Adam Korczynski (ADA Logics) and OSS-Fuzz for reporting this issue.
    
      This is CVE-2022-41715 and Go issue https://go.dev/issue/55949.
    
    View the release notes for more information: https://go.dev/doc/devel/release#go1.18.7
    
    Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
    thaJeztah committed Oct 4, 2022
    Copy the full SHA
    3e06ce8 View commit details
    Browse the repository at this point in the history