[ADMINAPI-1297] - Change the Tenant Endpoint to Read Only

[stephenfuqua]

No description provided.

[stephenfuqua]

This file was reformatted with csharpier, which we should be using regularly.

[github-actions]

Test Results

252 tests   251 ✅  10s ⏱️
  3 suites    1 💤
  3 files      0 ❌

Results for commit 93e34f2.

♻️ This comment has been updated with latest results.

[stephenfuqua]

Build failures are occurring because of a problem with the openssl alpine package. I need someone else's help to address that problem.

[github-actions]

🔍 Vulnerabilities of development:latest

📦 Image Reference development:latest

digest	sha256:1bc3fa0f05514b0f9433326930b7a7bf9cad0d880f4f5c07c73494ae673f4ff2
vulnerabilities
platform	linux/amd64
size	94 MB
packages	587

📦 Base Image alpine:3

also known as	3.20 3.20.3 latest
digest	sha256:33735bd63cf84d7e388d9f6d297d348c523c044410f553bd878c6d7829612735
vulnerabilities

xz 5.6.2-r1 (apk) pkg:apk/alpine/xz@5.6.2-r1?os_name=alpine&os_version=3.20 Affected range <=5.6.2-r1 Fixed version Not Fixed Description

busybox 1.36.1-r30 (apk) pkg:apk/alpine/busybox@1.36.1-r30?os_name=alpine&os_version=3.20 Affected range <=1.36.1-r30 Fixed version Not Fixed Description Affected range <=1.36.1-r30 Fixed version Not Fixed Description

[github-actions]

🔍 Vulnerabilities of v1-gateway:latest

📦 Image Reference v1-gateway:latest

digest	sha256:2b1e72392ebff55e7f898ef3fbc5835362a187a46e392d784b7354359209de7c
vulnerabilities
platform	linux/amd64
size	11 MB
packages	53

📦 Base Image nginx:1-alpine

also known as	1.21-alpine 1.21.6-alpine alpine mainline-alpine
digest	sha256:050385609d832fae11b007fbbfba77d0bba12bf72bc0dca0ac03e09b1998580f
vulnerabilities

curl 7.80.0-r0 (apk) pkg:apk/alpine/curl@7.80.0-r0?os_name=alpine&os_version=3.15 Affected range <8.4.0-r0 Fixed version 8.4.0-r0 Description Affected range <7.80.0-r4 Fixed version 7.80.0-r4 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <7.80.0-r4 Fixed version 7.80.0-r4 Description Affected range <7.80.0-r1 Fixed version 7.80.0-r1 Description Affected range <8.3.0-r0 Fixed version 8.3.0-r0 Description Affected range <8.1.0-r0 Fixed version 8.1.0-r0 Description Affected range <7.80.0-r5 Fixed version 7.80.0-r5 Description Affected range <7.80.0-r4 Fixed version 7.80.0-r4 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <7.80.0-r1 Fixed version 7.80.0-r1 Description Affected range <8.5.0-r0 Fixed version 8.5.0-r0 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <7.80.0-r1 Fixed version 7.80.0-r1 Description Affected range <8.1.0-r0 Fixed version 8.1.0-r0 Description Affected range <8.1.0-r0 Fixed version 8.1.0-r0 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <7.80.0-r5 Fixed version 7.80.0-r5 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Affected range <7.80.0-r1 Fixed version 7.80.0-r1 Description Affected range <8.0.1-r0 Fixed version 8.0.1-r0 Description Affected range <8.5.0-r0 Fixed version 8.5.0-r0 Description Affected range <7.80.0-r2 Fixed version 7.80.0-r2 Description Allocation of Resources Without Limits or Throttling Affected range <7.80.0-r6 Fixed version 7.80.0-r6 Description curl supports "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was capped, but the cap was implemented on a per-header basis allowing a malicious server to insert a virtually unlimited number of compression steps simply by using many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors. We are not aware of any exploit of this flaw. Affected range <8.4.0-r0 Fixed version 8.4.0-r0 Description Affected range <8.1.0-r0 Fixed version 8.1.0-r0 Description Affected range <7.80.0-r3 Fixed version 7.80.0-r3 Description Cleartext Transmission of Sensitive Information Affected range <7.80.0-r6 Fixed version 7.80.0-r6 Description curl's HSTS cache saving behaves wrongly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recently completed transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS. Reproducible like this: curl --hsts hsts.txt --parallel https://curl.se https://example.com curl --hsts hsts.txt http://curl.se We are not aware of any exploit of this flaw. Cleartext Transmission of Sensitive Information Affected range <7.80.0-r6 Fixed version 7.80.0-r6 Description curl's HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however suprisingly be ignored by subsequent transfers when done on the same command line because the state would not be properly carried on. Reproducible like this: curl --hsts "" https://curl.se http://curl.se The first URL returns HSTS information that the second URL fails to take advantage of. We are not aware of any exploit of this flaw.

pcre2 10.39-r0 (apk) pkg:apk/alpine/pcre2@10.39-r0?os_name=alpine&os_version=3.15 Affected range <10.40-r0 Fixed version 10.40-r0 Description Affected range <10.40-r0 Fixed version 10.40-r0 Description Affected range <10.42-r0 Fixed version 10.42-r0 Description

freetype 2.11.0-r0 (apk) pkg:apk/alpine/freetype@2.11.0-r0?os_name=alpine&os_version=3.15 Affected range <2.11.1-r1 Fixed version 2.11.1-r1 Description Affected range <2.11.1-r2 Fixed version 2.11.1-r2 Description Affected range <2.11.1-r2 Fixed version 2.11.1-r2 Description

zlib 1.2.11-r3 (apk) pkg:apk/alpine/zlib@1.2.11-r3?os_name=alpine&os_version=3.15 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

libxml2 2.9.12-r2 (apk) pkg:apk/alpine/libxml2@2.9.12-r2?os_name=alpine&os_version=3.15 Affected range <2.9.14-r2 Fixed version 2.9.14-r2 Description Affected range <2.9.14-r2 Fixed version 2.9.14-r2 Description Affected range <2.9.13-r0 Fixed version 2.9.13-r0 Description Affected range <2.9.14-r1 Fixed version 2.9.14-r1 Description Affected range <2.9.14-r0 Fixed version 2.9.14-r0 Description

openssl 1.1.1l-r7 (apk) pkg:apk/alpine/openssl@1.1.1l-r7?os_name=alpine&os_version=3.15 Affected range <1.1.1t-r2 Fixed version 1.1.1t-r2 Description Affected range <1.1.1n-r0 Fixed version 1.1.1n-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.1u-r0 Fixed version 1.1.1u-r0 Description Affected range <1.1.1w-r1 Fixed version 1.1.1w-r1 Description Affected range <1.1.1v-r0 Fixed version 1.1.1v-r0 Description Affected range <1.1.1u-r2 Fixed version 1.1.1u-r2 Description 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.

nghttp2 1.46.0-r0 (apk) pkg:apk/alpine/nghttp2@1.46.0-r0?os_name=alpine&os_version=3.15 Affected range <1.46.0-r2 Fixed version 1.46.0-r2 Description Affected range <1.46.0-r1 Fixed version 1.46.0-r1 Description

ncurses 6.3_p20211120-r0 (apk) pkg:apk/alpine/ncurses@6.3_p20211120-r0?os_name=alpine&os_version=3.15 Affected range <6.3_p20211120-r2 Fixed version 6.3_p20211120-r2 Description Affected range <6.3_p20211120-r1 Fixed version 6.3_p20211120-r1 Description

libwebp 1.2.2-r0 (apk) pkg:apk/alpine/libwebp@1.2.2-r0?os_name=alpine&os_version=3.15 Affected range <1.2.2-r2 Fixed version 1.2.2-r2 Description Affected range <1.2.2-r1 Fixed version 1.2.2-r1 Description

xz 5.2.5-r0 (apk) pkg:apk/alpine/xz@5.2.5-r0?os_name=alpine&os_version=3.15 Affected range <5.2.5-r1 Fixed version 5.2.5-r1 Description Affected range <=5.2.5-r1 Fixed version Not Fixed Description

busybox 1.34.1-r3 (apk) pkg:apk/alpine/busybox@1.34.1-r3?os_name=alpine&os_version=3.15 Affected range <1.34.1-r5 Fixed version 1.34.1-r5 Description Affected range <1.34.1-r5 Fixed version 1.34.1-r5 Description

libretls 3.3.4-r2 (apk) pkg:apk/alpine/libretls@3.3.4-r2?os_name=alpine&os_version=3.15 Affected range <3.3.4-r3 Fixed version 3.3.4-r3 Description

libxslt 1.1.34-r1 (apk) pkg:apk/alpine/libxslt@1.1.34-r1?os_name=alpine&os_version=3.15 Affected range <1.1.35-r0 Fixed version 1.1.35-r0 Description