bump golang 1.12.10 (CVE-2019-16276)
full diff: https://github.com/golang/go/compare/go1.12.9...go1.12.10
```
Hi gophers,
We have just released Go 1.13.1 and Go 1.12.10 to address a recently reported security issue. We recommend that all affected users update to one of these releases (if you're not sure which, choose Go 1.13.1).
net/http (through net/textproto) used to accept and normalize invalid HTTP/1.1 headers with a space before the colon, in violation of RFC 7230. If a Go server is used behind an uncommon reverse proxy that accepts and forwards but doesn't normalize such invalid headers, the reverse proxy and the server can interpret the headers differently. This can lead to filter bypasses or request smuggling, the latter if requests from separate clients are multiplexed onto the same upstream connection by the proxy. Such invalid headers are now rejected by Go servers, and passed without normalization to Go client applications.
The issue is CVE-2019-16276 and Go issue golang.org/issue/34540.
Thanks to Andrew Stucki, Adam Scarr (99designs.com), and Jan Masarik (masarik.sh) for discovering and reporting this issue.
Downloads are available at https://golang.org/dl for all supported platforms.
Alla prossima,
Filippo on behalf of the Go team
```
From the patch: https://github.com/golang/go/commit/6e6f4aaf70c8b1cc81e65a26332aa9409de03ad8
```
net/textproto: don't normalize headers with spaces before the colon
RFC 7230 is clear about headers with a space before the colon, like
X-Answer : 42
being invalid, but we've been accepting and normalizing them for compatibility
purposes since CL 5690059 in 2012.
On the client side, this is harmless and indeed most browsers behave the same
to this day. On the server side, this becomes a security issue when the
behavior doesn't match that of a reverse proxy sitting in front of the server.
For example, if a WAF accepts them without normalizing them, it might be
possible to bypass its filters, because the Go server would interpret the
header differently. Worse, if the reverse proxy coalesces requests onto a
single HTTP/1.1 connection to a Go server, the understanding of the request
boundaries can get out of sync between them, allowing an attacker to tack an
arbitrary method and path onto a request by other clients, including
authentication headers unknown to the attacker.
This was recently presented at multiple security conferences:
https://portswigger.net/blog/http-desync-attacks-request-smuggling-reborn
net/http servers already reject header keys with invalid characters.
Simply stop normalizing extra spaces in net/textproto, let it return them
unchanged like it does for other invalid headers, and let net/http enforce
RFC 7230, which is HTTP specific. This loses us normalization on the client
side, but there's no right answer on the client side anyway, and hiding the
issue sounds worse than letting the application decide.
```
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-09-27 17:30:54 -04:00
|
|
|
ARG GO_VERSION=1.12.10
|
2019-07-18 05:13:45 -04:00
|
|
|
|
|
|
|
|
FROM golang:${GO_VERSION}-alpine
|
2017-04-18 19:12:24 -04:00
|
|
|
|
2018-03-06 05:15:18 -05:00
|
|
|
RUN apk add -U git make bash coreutils ca-certificates curl
|
2017-04-18 19:12:24 -04:00
|
|
|
|
2019-05-14 19:13:27 -04:00
|
|
|
ARG VNDR_SHA=b177b583eb9d44bd5abfca3083a4aeb971b75861
|
2017-07-18 12:22:28 -04:00
|
|
|
RUN go get -d github.com/LK4D4/vndr && \
|
2017-07-11 14:19:02 -04:00
|
|
|
cd /go/src/github.com/LK4D4/vndr && \
|
|
|
|
|
git checkout -q "$VNDR_SHA" && \
|
2017-07-10 17:31:57 -04:00
|
|
|
go build -v -o /usr/bin/vndr . && \
|
2017-04-18 19:12:24 -04:00
|
|
|
rm -rf /go/src/* /go/pkg/* /go/bin/*
|
|
|
|
|
|
2018-02-12 13:03:31 -05:00
|
|
|
ARG ESC_SHA=58d9cde84f237ecdd89bd7f61c2de2853f4c5c6e
|
|
|
|
|
RUN go get -d github.com/mjibson/esc && \
|
|
|
|
|
cd /go/src/github.com/mjibson/esc && \
|
|
|
|
|
git checkout -q "$ESC_SHA" && \
|
|
|
|
|
go build -v -o /usr/bin/esc . && \
|
2017-05-09 15:37:22 -04:00
|
|
|
rm -rf /go/src/* /go/pkg/* /go/bin/*
|
|
|
|
|
|
2019-04-12 21:16:01 -04:00
|
|
|
ARG GOTESTSUM_VERSION=0.3.4
|
2019-01-24 11:53:42 -05:00
|
|
|
RUN curl -Ls https://github.com/gotestyourself/gotestsum/releases/download/v${GOTESTSUM_VERSION}/gotestsum_${GOTESTSUM_VERSION}_linux_amd64.tar.gz -o gotestsum.tar.gz && \
|
|
|
|
|
tar -xf gotestsum.tar.gz gotestsum -C /usr/bin && \
|
|
|
|
|
rm gotestsum.tar.gz
|
|
|
|
|
|
2017-08-04 21:24:21 -04:00
|
|
|
ENV CGO_ENABLED=0 \
|
2017-08-15 14:32:44 -04:00
|
|
|
PATH=$PATH:/go/src/github.com/docker/cli/build \
|
|
|
|
|
DISABLE_WARN_OUTSIDE_CONTAINER=1
|
2017-04-18 19:12:24 -04:00
|
|
|
WORKDIR /go/src/github.com/docker/cli
|
|
|
|
|
CMD sh
|
Do not patch Dockerfiles in CI
When building the Dockerfiles for development, those images are mainly used to
create a reproducible build-environment. The source code is bind-mounted into
the image at runtime; there is no need to create an image with the actual
source code, and copying the source code into the image would lead to a new
image being created for each code-change (possibly leading up to many "dangling"
images for previous code-changes).
However, when building (and using) the development images in CI, bind-mounting
is not an option, because the daemon is running remotely.
To make this work, the circle-ci script patched the Dockerfiles when CI is run;
adding a `COPY` to the respective Dockerfiles.
Patching Dockerfiles is not really a "best practice" and, even though the source
code does not and up in the image, the source would still be _sent_ to the daemon
for each build (unless BuildKit is used).
This patch updates the makefiles, circle-ci script, and Dockerfiles;
- When building the Dockerfiles locally, pipe the Dockerfile through stdin.
Doing so, prevents the build-context from being sent to the daemon. This speeds
up the build, and doesn't fill up the Docker "temp" directory with content that's
not used
- Now that no content is sent, add the COPY instructions to the Dockerfiles, and
remove the code in the circle-ci script to "live patch" the Dockerfiles.
Before this patch is applied (with cache):
```
$ time make -f docker.Makefile build_shell_validate_image
docker build -t docker-cli-shell-validate -f ./dockerfiles/Dockerfile.shellcheck .
Sending build context to Docker daemon 41MB
Step 1/2 : FROM debian:stretch-slim
...
Successfully built 81e14e8ad856
Successfully tagged docker-cli-shell-validate:latest
2.75 real 0.45 user 0.56 sys
```
After this patch is applied (with cache)::
```
$ time make -f docker.Makefile build_shell_validate_image
cat ./dockerfiles/Dockerfile.shellcheck | docker build -t docker-cli-shell-validate -
Sending build context to Docker daemon 2.048kB
Step 1/2 : FROM debian:stretch-slim
...
Successfully built 81e14e8ad856
Successfully tagged docker-cli-shell-validate:latest
0.33 real 0.07 user 0.08 sys
```
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-11-28 19:06:10 -05:00
|
|
|
COPY . .
|
