Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
Introduced through:
- helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
+ sigs.k8s.io/kustomize/kustomize/v4@* and golang.org/x/net/http2/hpack@v0.0.0-20220127200216-cd36cc0744dd
Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.0.0-20220906165146-f3363e06e74c, 1.18.6, 1.19.1 or higher.
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Introduced through:
- helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
+ helm.sh/helm/v3@* and golang.org/x/net/http2@v0.5.0
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Note:Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
-
Remediation
-
There is no fixed version for Ubuntu:22.04systemd.
Affected versions of this package are vulnerable to Incorrect Privilege Assignment such that when called with a non-zero flags parameter, the Faccessat function can incorrectly report that a file is accessible.
-
Remediation
-
Upgrade golang.org/x/sys/unix to version 0.1.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
-
Details
-
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
-
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
-
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
-
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
-
Two common types of DoS vulnerabilities:
-
-
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
-
-
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
-
-
-
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.4.0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
parse-url is an An advanced url parser supporting git urls too.
-
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to improper detection of protocol, resource, and pathname fields. Exploiting this vulnerability results in bypassing protocol verification.
+
parse-url is an An advanced url parser supporting git urls too.
+ Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to improper detection of protocol, resource, and pathname fields. Exploiting this vulnerability results in bypassing protocol verification.
PoC:
import parseUrl from "parse-url";
import fetch from 'node-fetch';
@@ -611,8 +2454,8 @@
Detailed paths
Overview
-
parse-url is an An advanced url parser supporting git urls too.
-
Affected versions of this package are vulnerable to Improper Input Validation due to incorrect parsing of URLs. This allows the attacker to craft a malformed URL which can lead to a phishing attack.
+
parse-url is an An advanced url parser supporting git urls too.
+ Affected versions of this package are vulnerable to Improper Input Validation due to incorrect parsing of URLs. This allows the attacker to craft a malformed URL which can lead to a phishing attack.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the braceExpand function in minimatch.js.
+
minimatch is a minimal matching utility.
+ Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the braceExpand function in minimatch.js.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
+
gopkg.in/yaml.v2 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
+
go.mongodb.org/mongo-driver/bson/bsonrw is a The MongoDB supported driver for Go.
+ Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
Remediation
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
References
diff --git a/docs/snyk/v2.5.12/ghcr.io_dexidp_dex_v2.35.3.html b/docs/snyk/v2.4.25/ghcr.io_dexidp_dex_v2.35.3.html
similarity index 91%
rename from docs/snyk/v2.5.12/ghcr.io_dexidp_dex_v2.35.3.html
rename to docs/snyk/v2.4.25/ghcr.io_dexidp_dex_v2.35.3.html
index 1b6c9d43d2a12..05cb82375bce1 100644
--- a/docs/snyk/v2.5.12/ghcr.io_dexidp_dex_v2.35.3.html
+++ b/docs/snyk/v2.4.25/ghcr.io_dexidp_dex_v2.35.3.html
@@ -7,7 +7,7 @@
Snyk test report
-
+
@@ -456,7 +456,7 @@
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Introduced through:
- sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20210107192922-496545a6307b
+ sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776
Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
PoC
package main
@@ -588,7 +597,7 @@
NULL Pointer Dereference
Introduced through:
- sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20210107192922-496545a6307b
+ sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776
Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
Remediation
Upgrade golang.org/x/net/http2 to version 0.0.0-20220906165146-f3363e06e74c, 1.18.6, 1.19.1 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Note:Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
+
Overview
+
Affected versions of this package are vulnerable to Denial of Service (DoS) when handling requests with non-standard HTTP methods.
+
Note: In order to be affected, an instrumented software must:
+
+
use promhttp.InstrumentHandler* middleware except RequestsInFlight
+
+
not filter any specific methods (e.g GET) before middleware
+
+
pass metric with method label name to the middleware
+
+
not have any firewall/LB/proxy that filters away requests with unknown method.
+
+
+
Workarounds:
+
+
removing the method label name from counter/gauge used in the InstrumentHandler
+
+
turning off affected promhttp handlers
+
+
adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request
+
+
using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
+
+
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
Upgrade Ubuntu:22.04tar to version 1.34+dfsg-1ubuntu0.1.22.04.1 or higher.
+
Upgrade github.com/prometheus/client_golang/prometheus/promhttp to version 1.11.1 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and systemd/libsystemd0@249.11-0ubuntu3.6
+ github.com/argoproj/argo-cd/v2@* and github.com/emicklei/go-restful@v2.9.5+incompatible
Note:Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
+
Overview
+
Affected versions of this package are vulnerable to Authorization Bypass when using CORS Filter with a configurable AllowedDomains parameter (which is an array of domains allowed in CORS policy), with the same value as exists in allowedOriginPatterns parameter (used for matching origin using regular expression), it causes for all domains in AllowedDomains to be also used as regular expression for matching origin validation.
+ This behavior means that if example.com exists in AllowedDomains, all domains starting with example.com would be acceptable, including example.com.hacker.domain.
Remediation
-
There is no fixed version for Ubuntu:22.04systemd.
+
Upgrade github.com/emicklei/go-restful to version 2.16.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
-
Details
-
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
-
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
-
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
-
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
-
Two common types of DoS vulnerabilities:
-
-
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
-
-
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
-
-
+
github.com/Masterminds/vcs is a VCS Repo management through a common interface in Go.
+ Affected versions of this package are vulnerable to Command Injection via argument injection. When hg is executed, argument strings are passed to hg in a way that additional flags can be set. The additional flags can be used to perform a command injection.
Introduced through:
- sigs.k8s.io/kustomize/kustomize/v4@* and golang.org/x/text/language@v0.3.7
+ github.com/argoproj/argo-cd/v2@* and gopkg.in/yaml.v2@v2.2.4
Affected versions of this package are vulnerable to Improper Input Validation due to the parser being, by design, exposed to untrusted user input, which can be leveraged to force a program to consume significant time parsing Accept-Language headers.
+
gopkg.in/yaml.v2 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
Upgrade golang.org/x/text/language to version 0.3.8 or higher.
+
Upgrade gopkg.in/yaml.v2 to version 2.2.8 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Introduced through:
- github.com/argoproj/argo-cd/v2@* and go.mongodb.org/mongo-driver/bson/bsonrw@v1.1.2
+ sigs.k8s.io/kustomize/kustomize/v4@* and golang.org/x/net/http/httpguts@v0.0.0-20201110031124-69a78807bb2b
Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
+
golang.org/x/net/http/httpguts is a package providing functions implementing various details of the HTTP specification
+ Affected versions of this package are vulnerable to Denial of Service (DoS) when processing a large header to ReadRequest or ReadResponse. Servers are only vulnerable if the default max header of 1MB is increased by setting Server.MaxHeaderBytes.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
+
Upgrade golang.org/x/net/http/httpguts to version 0.0.0-20210428140749-89ef3d95e781 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and gnutls28/libgnutls30@3.7.3-4ubuntu1.1
+ github.com/argoproj/argo-cd/v2@* and go.mongodb.org/mongo-driver/bson/bsonrw@v1.1.2
Note:Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
+
Overview
+
go.mongodb.org/mongo-driver/bson/bsonrw is a The MongoDB supported driver for Go.
+ Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
Remediation
-
Upgrade Ubuntu:22.04gnutls28 to version 3.7.3-4ubuntu1.2 or higher.
+
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and openssl/libssl3@3.0.2-0ubuntu1.8
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and openssl/libssl3@3.0.2-0ubuntu1.8
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and ncurses/libtinfo6@6.3-2
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and ncurses/libtinfo6@6.3-2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and gnupg2/gpgv@2.2.27-3ubuntu2.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and gnupg2/gpgv@2.2.27-3ubuntu2.1
Allocation of Resources Without Limits or Throttling
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and glibc/libc-bin@2.35-0ubuntu3.1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and glibc/libc-bin@2.35-0ubuntu3.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and coreutils@8.32-4.1ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and coreutils@8.32-4.1ubuntu1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.5.12 and bash@5.1-6ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.4.25 and bash@5.1-6ubuntu1
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
parse-url is an An advanced url parser supporting git urls too.
-
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to improper detection of protocol, resource, and pathname fields. Exploiting this vulnerability results in bypassing protocol verification.
+
parse-url is an An advanced url parser supporting git urls too.
+ Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to improper detection of protocol, resource, and pathname fields. Exploiting this vulnerability results in bypassing protocol verification.
PoC:
import parseUrl from "parse-url";
import fetch from 'node-fetch';
@@ -611,8 +2462,8 @@
Detailed paths
Overview
-
parse-url is an An advanced url parser supporting git urls too.
-
Affected versions of this package are vulnerable to Improper Input Validation due to incorrect parsing of URLs. This allows the attacker to craft a malformed URL which can lead to a phishing attack.
+
parse-url is an An advanced url parser supporting git urls too.
+ Affected versions of this package are vulnerable to Improper Input Validation due to incorrect parsing of URLs. This allows the attacker to craft a malformed URL which can lead to a phishing attack.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the braceExpand function in minimatch.js.
+
minimatch is a minimal matching utility.
+ Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the braceExpand function in minimatch.js.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
+
gopkg.in/yaml.v2 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
+
go.mongodb.org/mongo-driver/bson/bsonrw is a The MongoDB supported driver for Go.
+ Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
Remediation
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
References
diff --git a/docs/snyk/v2.6.3/ghcr.io_dexidp_dex_v2.35.3.html b/docs/snyk/v2.5.13/ghcr.io_dexidp_dex_v2.35.3.html
similarity index 91%
rename from docs/snyk/v2.6.3/ghcr.io_dexidp_dex_v2.35.3.html
rename to docs/snyk/v2.5.13/ghcr.io_dexidp_dex_v2.35.3.html
index fe33f32907baf..3d2d890d7eb92 100644
--- a/docs/snyk/v2.6.3/ghcr.io_dexidp_dex_v2.35.3.html
+++ b/docs/snyk/v2.5.13/ghcr.io_dexidp_dex_v2.35.3.html
@@ -7,7 +7,7 @@
Snyk test report
-
+
@@ -456,7 +456,7 @@
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
Introduced through:
- github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.4.0
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2/hpack@v0.0.0-20220621193019-9d032be2e588
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
@@ -717,7 +725,7 @@
Details
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.7.0 or higher.
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Introduced through:
- helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.0.0-20220621193019-9d032be2e588
Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
Remediation
Upgrade golang.org/x/net/http2 to version 0.0.0-20220906165146-f3363e06e74c, 1.18.6, 1.19.1 or higher.
Note:Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
+
Overview
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
Upgrade Ubuntu:22.04tar to version 1.34+dfsg-1ubuntu0.1.22.04.1 or higher.
+
Upgrade golang.org/x/net/http2 to version 0.7.0 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and systemd/libsystemd0@249.11-0ubuntu3.6
+ github.com/argoproj/argo-cd/v2@* and gopkg.in/yaml.v2@v2.2.4
Note:Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
+
Overview
+
gopkg.in/yaml.v2 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
There is no fixed version for Ubuntu:22.04systemd.
+
Upgrade gopkg.in/yaml.v2 to version 2.2.8 or higher.
Introduced through:
- helm.sh/helm/v3@* and golang.org/x/sys/unix@v0.0.0-20220722155257-8c9f86f7a55f
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/sys/unix@v0.0.0-20220520151302-bc2c85ada10a
Introduced through:
- helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.0.0-20220621193019-9d032be2e588
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and gnutls28/libgnutls30@3.7.3-4ubuntu1.1
+ github.com/argoproj/argo-cd/v2@* and go.mongodb.org/mongo-driver/bson/bsonrw@v1.1.2
Note:Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
+
Overview
+
go.mongodb.org/mongo-driver/bson/bsonrw is a The MongoDB supported driver for Go.
+ Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
Remediation
-
Upgrade Ubuntu:22.04gnutls28 to version 3.7.3-4ubuntu1.2 or higher.
+
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and openssl/libssl3@3.0.2-0ubuntu1.8
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and openssl/libssl3@3.0.2-0ubuntu1.8
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and ncurses/libtinfo6@6.3-2
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and ncurses/libtinfo6@6.3-2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and gnupg2/gpgv@2.2.27-3ubuntu2.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and gnupg2/gpgv@2.2.27-3ubuntu2.1
Allocation of Resources Without Limits or Throttling
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and glibc/libc-bin@2.35-0ubuntu3.1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and glibc/libc-bin@2.35-0ubuntu3.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and coreutils@8.32-4.1ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and coreutils@8.32-4.1ubuntu1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.6.3 and bash@5.1-6ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.5.13 and bash@5.1-6ubuntu1
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.16.
- See How to fix? for Alpine:3.16 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.16openssl to version 1.1.1t-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
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.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine:3.17.
- See How to fix? for Alpine:3.17 relevant fixed versions and status.
-
A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.
-
Remediation
-
Upgrade Alpine:3.17openssl to version 3.0.8-r0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
diff --git a/docs/snyk/v2.4.24/ghcr.io_dexidp_dex_v2.35.3.html b/docs/snyk/v2.6.4/ghcr.io_dexidp_dex_v2.35.3.html
similarity index 91%
rename from docs/snyk/v2.4.24/ghcr.io_dexidp_dex_v2.35.3.html
rename to docs/snyk/v2.6.4/ghcr.io_dexidp_dex_v2.35.3.html
index 0e88b5353bf75..4a7964a393c76 100644
--- a/docs/snyk/v2.4.24/ghcr.io_dexidp_dex_v2.35.3.html
+++ b/docs/snyk/v2.6.4/ghcr.io_dexidp_dex_v2.35.3.html
@@ -7,7 +7,7 @@
Snyk test report
-
+
@@ -456,7 +456,7 @@
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
+
Remediation
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
Introduced through:
- sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776
+ sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20210107192922-496545a6307b
Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) via the Unmarshal function, which causes the program to crash when attempting to deserialize invalid input.
PoC
package main
@@ -597,7 +588,7 @@
NULL Pointer Dereference
Introduced through:
- sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776
+ sigs.k8s.io/kustomize/kustomize/v4@* and gopkg.in/yaml.v3@v3.0.0-20210107192922-496545a6307b
Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
+
gopkg.in/yaml.v3 is a YAML support package for the Go language.
+ Affected versions of this package are vulnerable to NULL Pointer Dereference when parsing #\n-\n-\n0 via the parserc.go parser.
Introduced through:
- github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.0.0-20220621193019-9d032be2e588
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2/hpack@v0.4.0
Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
-
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.0.0-20220906165146-f3363e06e74c, 1.18.6, 1.19.1 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
@@ -810,7 +725,7 @@
Details
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.7.0 or higher.
+
Upgrade golang.org/x/net/http2/hpack to version 0.7.0 or higher.
Introduced through:
- helm.sh/helm/v3@* and github.com/prometheus/client_golang/prometheus/promhttp@v1.11.0
+ github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.4.0
Affected versions of this package are vulnerable to Denial of Service (DoS) when handling requests with non-standard HTTP methods.
-
Note: In order to be affected, an instrumented software must:
-
-
use promhttp.InstrumentHandler* middleware except RequestsInFlight
-
-
not filter any specific methods (e.g GET) before middleware
-
-
pass metric with method label name to the middleware
-
-
not have any firewall/LB/proxy that filters away requests with unknown method.
-
-
-
Workarounds:
-
-
removing the method label name from counter/gauge used in the InstrumentHandler
-
-
turning off affected promhttp handlers
-
-
adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request
-
-
using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
-
-
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) such that a maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
@@ -911,25 +814,24 @@
Details
Remediation
-
Upgrade github.com/prometheus/client_golang/prometheus/promhttp to version 1.11.1 or higher.
+
Upgrade golang.org/x/net/http2 to version 0.7.0 or higher.
Introduced through:
- github.com/argoproj/argo-cd/v2@* and github.com/emicklei/go-restful@v2.9.5+incompatible
+ helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
Affected versions of this package are vulnerable to Authorization Bypass when using CORS Filter with a configurable AllowedDomains parameter (which is an array of domains allowed in CORS policy), with the same value as exists in allowedOriginPatterns parameter (used for matching origin using regular expression), it causes for all domains in AllowedDomains to be also used as regular expression for matching origin validation.
- This behavior means that if example.com exists in AllowedDomains, all domains starting with example.com would be acceptable, including example.com.hacker.domain.
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service as an HTTP/2 connection can hang during closing if a shutdown was preempted by a fatal error.
Remediation
-
Upgrade github.com/emicklei/go-restful to version 2.16.0 or higher.
+
Upgrade golang.org/x/net/http2 to version 0.0.0-20220906165146-f3363e06e74c, 1.18.6, 1.19.1 or higher.
Introduced through:
- helm.sh/helm/v3@* and github.com/Masterminds/vcs@v1.13.1
+ sigs.k8s.io/kustomize/kustomize/v4@* and golang.org/x/text/language@v0.3.7
Affected versions of this package are vulnerable to Command Injection via argument injection. When hg is executed, argument strings are passed to hg in a way that additional flags can be set. The additional flags can be used to perform a command injection.
Affected versions of this package are vulnerable to Improper Input Validation due to the parser being, by design, exposed to untrusted user input, which can be leveraged to force a program to consume significant time parsing Accept-Language headers.
Remediation
-
Upgrade github.com/Masterminds/vcs to version 1.13.3 or higher.
+
Upgrade golang.org/x/text/language to version 0.3.8 or higher.
Note:Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
+
Overview
+
Affected versions of this package are vulnerable to Incorrect Privilege Assignment such that when called with a non-zero flags parameter, the Faccessat function can incorrectly report that a file is accessible.
Remediation
-
Upgrade Ubuntu:22.04tar to version 1.34+dfsg-1ubuntu0.1.22.04.1 or higher.
+
Upgrade golang.org/x/sys/unix to version 0.1.0 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and systemd/libsystemd0@249.11-0ubuntu3.6
+ helm.sh/helm/v3@* and golang.org/x/net/http2@v0.0.0-20220722155237-a158d28d115b
Note:Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
+
Overview
+
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
+ Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
+
Details
+
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
+
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
+
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
+
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
+
Two common types of DoS vulnerabilities:
+
+
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
+
+
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
+
+
Remediation
-
There is no fixed version for Ubuntu:22.04systemd.
Affected versions of this package are vulnerable to Denial of Service (DoS). It is possible for authorized users to send malicious YAML payloads to cause kube-apiserver to consume excessive CPU cycles while parsing YAML.
-
Details
-
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
-
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
-
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
-
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
-
Two common types of DoS vulnerabilities:
-
-
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
-
-
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
-
-
-
Remediation
-
Upgrade gopkg.in/yaml.v2 to version 2.2.8 or higher.
Affected versions of this package are vulnerable to Incorrect Privilege Assignment such that when called with a non-zero flags parameter, the Faccessat function can incorrectly report that a file is accessible.
-
Remediation
-
Upgrade golang.org/x/sys/unix to version 0.1.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper checks and limitations for the number of entries in the cache, which can allow an attacker to consume unbounded amounts of memory by sending a small number of very large keys.
-
Details
-
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
-
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
-
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
-
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
-
Two common types of DoS vulnerabilities:
-
-
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
-
-
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
-
-
-
Remediation
-
Upgrade golang.org/x/net/http2 to version 0.4.0 or higher.
+
Upgrade golang.org/x/net/http2 to version 0.4.0 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS) when processing a large header to ReadRequest or ReadResponse. Servers are only vulnerable if the default max header of 1MB is increased by setting Server.MaxHeaderBytes.
-
Details
-
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
-
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
-
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
-
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
-
Two common types of DoS vulnerabilities:
-
-
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
-
-
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package
-
-
-
Remediation
-
Upgrade golang.org/x/net/http/httpguts to version 0.0.0-20210428140749-89ef3d95e781 or higher.
Affected versions of this package are vulnerable to Improper Input Validation. Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents.
-
Remediation
-
Upgrade go.mongodb.org/mongo-driver/bson/bsonrw to version 1.5.1 or higher.
Note:Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu:22.04.
- See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
-
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
-
Remediation
-
Upgrade Ubuntu:22.04gnutls28 to version 3.7.3-4ubuntu1.2 or higher.
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and patch@2.7.6-7build2
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and patch@2.7.6-7build2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and openssl/libssl3@3.0.2-0ubuntu1.8
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and openssl/libssl3@3.0.2-0ubuntu1.8
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and openssh/openssh-client@1:8.9p1-3ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and ncurses/libtinfo6@6.3-2
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and ncurses/libtinfo6@6.3-2
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and krb5/libk5crypto3@1.19.2-2ubuntu0.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and gnupg2/gpgv@2.2.27-3ubuntu2.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and gnupg2/gpgv@2.2.27-3ubuntu2.1
Allocation of Resources Without Limits or Throttling
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and glibc/libc-bin@2.35-0ubuntu3.1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and glibc/libc-bin@2.35-0ubuntu3.1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and coreutils@8.32-4.1ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and coreutils@8.32-4.1ubuntu1
Introduced through:
- docker-image|quay.io/argoproj/argocd@v2.4.24 and bash@5.1-6ubuntu1
+ docker-image|quay.io/argoproj/argocd@v2.6.4 and bash@5.1-6ubuntu1