Publish v1.4.0 release

[eunomie]

No description provided.

[github-actions]

Your image	docker/scout-demo-service:fix
Current base image	alpine:3.18
Updated base image	alpine:3.19

[github-actions]

Your image	docker/scout-demo-service:main
Current base image	alpine:3.14
Updated base image	alpine:3.16

[github-actions]

🔍 Vulnerabilities of docker/scout-demo-service:main

📦 Image Reference docker/scout-demo-service:main

digest	sha256:c3dad839553c91a69b4959415f621289ffa9ee602b151ee0d0a0522100690ff5
vulnerabilities
platform	linux/amd64
size	19 MB
packages	80

📦 Base Image alpine:3

also known as	3.14 3.14.1 latest
digest	sha256:be9bdc0ef8e96dbc428dc189b31e2e3b05523d96d12ed627c37aa2936653258c
vulnerabilities

libssl1.1 1.1.1k-r0 (apk) pkg:apk/alpine/libssl1.1@1.1.1k-r0?arch=x86_64&upstream=openssl&distro=alpine-3.14.1 # Dockerfile (1:1) FROM alpine:3.14@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae Affected range <1.1.1l-r0 Fixed version 1.1.1l-r0 Description Affected range <1.1.1t-r1 Fixed version 1.1.1t-r1 Description Affected range <1.1.1n-r0 Fixed version 1.1.1n-r0 Description Affected range <1.1.1l-r0 Fixed version 1.1.1l-r0 Description Affected range <1.1.1t-r0 Fixed version 1.1.1t-r0 Description There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network. OpenSSL versions 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8. OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t. OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zg (premium support customers only). This issue was reported on 11th January 2023 by David Benjamin (Google). The fix was developed by Hugo Landau. Affected range <1.1.1t-r2 Fixed version 1.1.1t-r2 Description Affected range <1.1.1q-r0 Fixed version 1.1.1q-r0 Description Affected range <1.1.1t-r0 Fixed version 1.1.1t-r0 Description The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected. OpenSSL 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8. OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t. OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zg (premium support customers only). This issue was reported on 29th November 2022 by Octavio Galland and Marcel Böhme (Max Planck Institute for Security and Privacy). The fix was developed by Viktor Dukhovni and Matt Caswell. Affected range <1.1.1t-r0 Fixed version 1.1.1t-r0 Description The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. OpenSSL 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8. OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t. OpenSSL 1.0.2 is not affected by this issue. This issue was discovered by CarpetFuzz and reported on 8th December 2022 by Dawei Wang. The fix was developed by Kurt Roeckx and Matt Caswell. Affected range <1.1.1t-r0 Fixed version 1.1.1t-r0 Description A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. OpenSSL 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8. OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t. OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zg (premium support customers only). An initial report of a possible timing side channel was made on 14th July 2020 by Hubert Kario (Red Hat). A refined report identifying a specific timing side channel was made on 15th July 2022 by Hubert Kario. The fix was developed by Dmitry Belyavsky (Red Hat) and Hubert Kario.

zlib 1.2.11-r3 (apk) pkg:apk/alpine/zlib@1.2.11-r3?arch=x86_64&distro=alpine-3.14.1 # Dockerfile (1:1) FROM alpine:3.14@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae Affected range <1.2.12-r2 Fixed version 1.2.12-r2 Description Affected range <1.2.12-r0 Fixed version 1.2.12-r0 Description

ssl_client 1.33.1-r3 (apk) pkg:apk/alpine/ssl_client@1.33.1-r3?arch=x86_64&upstream=busybox&distro=alpine-3.14.1 # Dockerfile (1:1) FROM alpine:3.14@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae Affected range <1.33.1-r7 Fixed version 1.33.1-r7 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r6 Fixed version 1.33.1-r6 Description Affected range <1.33.1-r5 Fixed version 1.33.1-r5 Description Affected range <1.33.1-r4 Fixed version 1.33.1-r4 Description Affected range <1.33.1-r7 Fixed version 1.33.1-r7 Description

qs 6.7.0 (npm) pkg:npm/qs@6.7.0 # Dockerfile (14:17) RUN apk add --no-cache npm \ && npm i --no-optional \ && npm cache clean --force \ && apk del npm Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affected range >=6.7.0 <6.7.3 Fixed version 6.7.3 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description qs before 6.10.3 allows attackers to cause a Node process hang because an __ proto__ key can be used. In many typical web framework use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4.

express 4.17.1 (npm) pkg:npm/express@4.17.1 # Dockerfile (14:17) RUN apk add --no-cache npm \ && npm i --no-optional \ && npm cache clean --force \ && apk del npm OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <4.17.3 Fixed version 4.17.3 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[proto]=b&a[proto]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).

libretls 3.3.3p1-r2 (apk) pkg:apk/alpine/libretls@3.3.3p1-r2?arch=x86_64&distro=alpine-3.14.1 # Dockerfile (1:1) FROM alpine:3.14@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae Affected range <3.3.3p1-r3 Fixed version 3.3.3p1-r3 Description

[github-actions]

Overview

Image reference	docker/scout-demo-service:fix	docker/scout-demo-service:main
- digest	33a1d0839f98	c3dad839553c
- provenance		docker/scout-demo-service@7c3a067
- vulnerabilities
- platform	linux/amd64	linux/amd64
- size	26 MB	19 MB (-6.7 MB)
- packages	82	80 (-2)
Base Image	alpine:3.18 also known as: • 3.18.6	alpine:3.14 also known as: • 3 • latest
- vulnerabilities

Labels (9 changes)

• + 9 added

+com.docker.image.source.entrypoint=Dockerfile
+org.opencontainers.image.created=2023-12-17T11:59:19.246Z
+org.opencontainers.image.description=
+org.opencontainers.image.licenses=
+org.opencontainers.image.revision=7c3a06793fc8f97961b4a40c73e0f7ed85501857
+org.opencontainers.image.source=https://github.com/docker/scout-demo-service
+org.opencontainers.image.title=scout-demo-service
+org.opencontainers.image.url=https://github.com/docker/scout-demo-service
+org.opencontainers.image.version=main

Packages and Vulnerabilities (49 package changes and 26 vulnerability changes)

• ➕ 4 packages added
• ➖ 13 packages removed
• ♾️ 32 packages changed
• 36 packages unchanged

• ❗ 26 vulnerabilities added

Changes for packages of type apk (33 changes)

	Package	Version docker/scout-demo-service:fix	Version docker/scout-demo-service:main
♾️	alpine-baselayout	3.4.3-r1	3.2.0-r16
➖	alpine-baselayout-data	3.4.3-r1
♾️	alpine-keys	2.4-r1	2.3-r1
♾️	apk-tools	2.14.0-r2	2.12.7-r0
➖	brotli	1.0.9-r14
♾️	brotli-libs	1.0.9-r14	1.0.9-r5
♾️	busybox	1.36.1-r5	1.33.1-r3
➖	busybox-binsh	1.36.1-r5
♾️	c-ares	1.19.1-r0	1.17.2-r0
♾️	ca-certificates-bundle	20230506-r0	20191127-r5
➖	gcc	12.2.1_git20220924-r10
➖	icu	73.2-r2
➖	icu-data-en	73.2-r2
➖	icu-libs	73.2-r2
➖	libc-dev	0.7.2-r5
♾️	libc-utils	0.7.2-r5	0.7.2-r3
➕	libcrypto1.1		1.1.1k-r0
➖	libcrypto3	3.1.4-r5
♾️	libgcc	12.2.1_git20220924-r10	10.3.1_git20210424-r2
➕	libretls		3.3.3p1-r2
			Added vulnerabilities (1):
➕	libssl1.1		1.1.1k-r0
			Added vulnerabilities (10):
➖	libssl3	3.1.4-r5
♾️	libstdc++	12.2.1_git20220924-r10	10.3.1_git20210424-r2
♾️	musl	1.2.4-r2	1.2.2-r3
♾️	musl-utils	1.2.4-r2	1.2.2-r3
➖	nghttp2	1.57.0-r0
♾️	nghttp2-libs	1.57.0-r0	1.43.0-r0
♾️	nodejs	18.18.2-r0	14.21.3-r0
➖	openssl	3.1.4-r5
➖	pax-utils	1.3.7-r1
♾️	scanelf	1.3.7-r1	1.3.2-r0
♾️	ssl_client	1.36.1-r5	1.33.1-r3
			Added vulnerabilities (13):
♾️	zlib	1.2.13-r1	1.2.11-r3
			Added vulnerabilities (2):

Changes for packages of type generic (1 changes)

	Package	Version docker/scout-demo-service:fix	Version docker/scout-demo-service:main
➕	node		14.21.3

Changes for packages of type npm (15 changes)

	Package	Version docker/scout-demo-service:fix	Version docker/scout-demo-service:main
♾️	body-parser	1.19.2	1.19.0
♾️	bytes	3.1.2	3.1.0
♾️	content-disposition	0.5.4	0.5.3
♾️	cookie	0.4.2	0.4.0
♾️	express	4.17.3	4.17.1
			Added vulnerabilities (1):
♾️	http-errors	1.8.1	1.7.2
♾️	inherits	2.0.4	2.0.3
♾️	ms	2.1.3	2.1.1
♾️	qs	6.9.7	6.7.0
			Added vulnerabilities (1):
♾️	raw-body	2.4.3	2.4.0
♾️	safe-buffer	5.2.1	5.1.2
♾️	send	0.17.2	0.17.1
♾️	serve-static	1.14.2	1.14.1
♾️	setprototypeof	1.2.0	1.1.1
♾️	toidentifier	1.0.1	1.0.0