2022-03-17 05:37:08 -04:00
|
|
|
# syntax=docker/dockerfile:1
|
2017-05-02 15:10:03 -04:00
|
|
|
|
Update to go 1.19.2 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.19.2
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-10-04 14:51:47 -04:00
|
|
|
ARG GO_VERSION=1.19.2
|
2022-09-02 15:24:26 -04:00
|
|
|
ARG GOLANGCI_LINT_VERSION=v1.49.0
|
2017-05-02 15:10:03 -04:00
|
|
|
|
2021-08-05 02:44:16 -04:00
|
|
|
FROM golangci/golangci-lint:${GOLANGCI_LINT_VERSION}-alpine AS golangci-lint
|
2017-05-02 15:10:03 -04:00
|
|
|
|
2021-08-05 02:44:16 -04:00
|
|
|
FROM golang:${GO_VERSION}-alpine AS lint
|
|
|
|
|
ENV GO111MODULE=off
|
|
|
|
|
ENV CGO_ENABLED=0
|
|
|
|
|
ENV GOGC=75
|
2019-04-02 11:27:12 -04:00
|
|
|
WORKDIR /go/src/github.com/docker/cli
|
2021-08-05 02:44:16 -04:00
|
|
|
COPY --from=golangci-lint /usr/bin/golangci-lint /usr/bin/golangci-lint
|
|
|
|
|
RUN --mount=type=bind,target=. \
|
|
|
|
|
--mount=type=cache,target=/root/.cache \
|
|
|
|
|
golangci-lint run
|
