-
-
Path Traversal
-
-
-
- critical severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Path Traversal via malicious server replies. An attacker can create and amend files across the filesystem and potentially achieve remote code execution by sending crafted responses to the client.
-
Notes:
-
- This is only exploitable if the client is using ChrootOS, which is the default for certain functions such as PlainClone.
- Applications using BoundOS or in-memory filesystems are not affected by this issue.
- Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.
-
-
Workaround
-
This vulnerability can be mitigated by limiting the client's use to trustworthy Git servers.
-
-
Upgrade github.com/go-git/go-git/v5 to version 5.11.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Out-of-bounds Write
-
-
-
- critical severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream busybox package and not the busybox package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution.
-
-
Upgrade Alpine:3.18 busybox to version 1.36.1-r1 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2023-5363
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: A bug has been identified in the processing of key and
- initialisation vector (IV) lengths. This can lead to potential truncation
- or overruns during the initialisation of some symmetric ciphers.
-
Impact summary: A truncation in the IV can result in non-uniqueness,
- which could result in loss of confidentiality for some cipher modes.
-
When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or
- EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after
- the key and IV have been established. Any alterations to the key length,
- via the "keylen" parameter or the IV length, via the "ivlen" parameter,
- within the OSSL_PARAM array will not take effect as intended, potentially
- causing truncation or overreading of these values. The following ciphers
- and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.
-
For the CCM, GCM and OCB cipher modes, truncation of the IV can result in
- loss of confidentiality. For example, when following NIST's SP 800-38D
- section 8.2.1 guidance for constructing a deterministic IV for AES in
- GCM mode, truncation of the counter portion could lead to IV reuse.
-
Both truncations and overruns of the key and overruns of the IV will
- produce incorrect results and could, in some cases, trigger a memory
- exception. However, these issues are not currently assessed as security
- critical.
-
Changing the key and/or IV lengths is not considered to be a common operation
- and the vulnerable API was recently introduced. Furthermore it is likely that
- application developers will have spotted this problem during testing since
- decryption would fail unless both peers in the communication were similarly
- vulnerable. For these reasons we expect the probability of an application being
- vulnerable to this to be quite low. However if an application is vulnerable then
- this issue is considered very serious. For these reasons we have assessed this
- issue as Moderate severity overall.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
-
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because
- the issue lies outside of the FIPS provider boundary.
-
OpenSSL 3.1 and 3.0 are vulnerable to this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Denial of Service (DoS)
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
google.golang.org/grpc is a Go implementation of gRPC
-
Affected versions of this package are vulnerable to Denial of Service (DoS) in the implementation of the HTTP/2 protocol. An attacker can cause a denial of service (including via DDoS) by rapidly resetting many streams through request cancellation.
-
-
Upgrade google.golang.org/grpc to version 1.56.3, 1.57.1, 1.58.3 or higher.
-
References
-
-
-
-
-
-
-
-
-
Denial of Service (DoS)
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
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) in the implementation of the HTTP/2 protocol. An attacker can cause a denial of service (including via DDoS) by rapidly resetting many streams through request cancellation.
-
-
Upgrade golang.org/x/net/http2 to version 0.17.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Allocation of Resources Without Limits or Throttling
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
-
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling when reading header data from CONTINUATION frames. As part of the HPACK flow, all incoming HEADERS and CONTINUATION frames are read even if their payloads exceed MaxHeaderBytes and will be discarded. An attacker can send excessive data over a connection to render it unresponsive.
-
-
Upgrade golang.org/x/net/http2 to version 0.23.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Heap-based Buffer Overflow
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via the sessionReadRecord function in the ext/session/sqlite3session.c file. An attacker can cause a program crash or execute arbitrary code by manipulating the input to trigger a heap-based buffer overflow.
-
-
Upgrade github.com/mattn/go-sqlite3 to version 1.14.18 or higher.
-
References
-
-
-
-
-
-
-
-
-
Denial of Service (DoS)
-
-
-
- high severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Denial of Service (DoS) when decrypting JWE inputs. An attacker can cause a denial-of-service by providing a PBES2 encrypted JWE blob with a very large p2c value.
-
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
-
-
-
Upgrade github.com/go-jose/go-jose/v3 to version 3.0.1 or higher.
-
References
-
-
-
-
-
-
-
-
-
Improper Authentication
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: The AES-SIV cipher implementation contains a bug that causes
- it to ignore empty associated data entries which are unauthenticated as
- a consequence.
-
Impact summary: Applications that use the AES-SIV algorithm and want to
- authenticate empty data entries as associated data can be mislead by removing
- adding or reordering such empty entries as these are ignored by the OpenSSL
- implementation. We are currently unaware of any such applications.
-
The AES-SIV algorithm allows for authentication of multiple associated
- data entries along with the encryption. To authenticate empty data the
- application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with
- NULL pointer as the output buffer and 0 as the input buffer length.
- The AES-SIV implementation in OpenSSL just returns success for such a call
- instead of performing the associated data authentication operation.
- The empty data thus will not be authenticated.
-
As this issue does not affect non-empty associated data authentication and
- we expect it to be rare for an application to use empty associated data
- entries this is qualified as Low severity issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.1-r2 or higher.
-
References
-
-
-
-
-
-
-
-
-
Inefficient Regular Expression Complexity
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Checking excessively long DH keys or parameters may be very slow.
-
Impact summary: Applications that use the functions DH_check(), DH_check_ex()
- or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long
- delays. Where the key or parameters that are being checked have been obtained
- from an untrusted source this may lead to a Denial of Service.
-
The function DH_check() performs various checks on DH parameters. One of those
- checks confirms that the modulus ('p' parameter) is not too large. Trying to use
- a very large modulus is slow and OpenSSL will not normally use a modulus which
- is over 10,000 bits in length.
-
However the DH_check() function checks numerous aspects of the key or parameters
- that have been supplied. Some of those checks use the supplied modulus value
- even if it has already been found to be too large.
-
An application that calls DH_check() and supplies a key or parameters obtained
- from an untrusted source could be vulernable to a Denial of Service attack.
-
The function DH_check() is itself called by a number of other OpenSSL functions.
- An application calling any of those other functions may similarly be affected.
- The other functions affected by this are DH_check_ex() and
- EVP_PKEY_param_check().
-
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications
- when using the '-check' option.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
- The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.1-r3 or higher.
-
References
-
-
-
-
-
-
-
-
-
Excessive Iteration
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Checking excessively long DH keys or parameters may be very slow.
-
Impact summary: Applications that use the functions DH_check(), DH_check_ex()
- or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long
- delays. Where the key or parameters that are being checked have been obtained
- from an untrusted source this may lead to a Denial of Service.
-
The function DH_check() performs various checks on DH parameters. After fixing
- CVE-2023-3446 it was discovered that a large q parameter value can also trigger
- an overly long computation during some of these checks. A correct q value,
- if present, cannot be larger than the modulus p parameter, thus it is
- unnecessary to perform these checks if q is larger than p.
-
An application that calls DH_check() and supplies a key or parameters obtained
- from an untrusted source could be vulnerable to a Denial of Service attack.
-
The function DH_check() is itself called by a number of other OpenSSL functions.
- An application calling any of those other functions may similarly be affected.
- The other functions affected by this are DH_check_ex() and
- EVP_PKEY_param_check().
-
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications
- when using the "-check" option.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
-
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.2-r0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Improper Check for Unusual or Exceptional Conditions
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Generating excessively long X9.42 DH keys or checking
- excessively long X9.42 DH keys or parameters may be very slow.
-
Impact summary: Applications that use the functions DH_generate_key() to
- generate an X9.42 DH key may experience long delays. Likewise, applications
- that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check()
- to check an X9.42 DH key or X9.42 DH parameters may experience long delays.
- Where the key or parameters that are being checked have been obtained from
- an untrusted source this may lead to a Denial of Service.
-
While DH_check() performs all the necessary checks (as of CVE-2023-3817),
- DH_check_pub_key() doesn't make any of these checks, and is therefore
- vulnerable for excessively large P and Q parameters.
-
Likewise, while DH_generate_key() performs a check for an excessively large
- P, it doesn't check for an excessively large Q.
-
An application that calls DH_generate_key() or DH_check_pub_key() and
- supplies a key or parameters obtained from an untrusted source could be
- vulnerable to a Denial of Service attack.
-
DH_generate_key() and DH_check_pub_key() are also called by a number of
- other OpenSSL functions. An application calling any of those other
- functions may similarly be affected. The other functions affected by this
- are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().
-
Also vulnerable are the OpenSSL pkey command line application when using the
- "-pubcheck" option, as well as the OpenSSL genpkey command line application.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
-
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r1 or higher.
-
References
-
-
-
-
-
-
-
-
-
Out-of-bounds Write
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: The POLY1305 MAC (message authentication code) implementation
- contains a bug that might corrupt the internal state of applications running
- on PowerPC CPU based platforms if the CPU provides vector instructions.
-
Impact summary: If an attacker can influence whether the POLY1305 MAC
- algorithm is used, the application state might be corrupted with various
- application dependent consequences.
-
The POLY1305 MAC (message authentication code) implementation in OpenSSL for
- PowerPC CPUs restores the contents of vector registers in a different order
- than they are saved. Thus the contents of some of these vector registers
- are corrupted when returning to the caller. The vulnerable code is used only
- on newer PowerPC processors supporting the PowerISA 2.07 instructions.
-
The consequences of this kind of internal application state corruption can
- be various - from no consequences, if the calling application does not
- depend on the contents of non-volatile XMM registers at all, to the worst
- consequences, where the attacker could get complete control of the application
- process. However unless the compiler uses the vector registers for storing
- pointers, the most likely consequence, if any, would be an incorrect result
- of some application dependent calculations or a crash leading to a denial of
- service.
-
The POLY1305 MAC algorithm is most frequently used as part of the
- CHACHA20-POLY1305 AEAD (authenticated encryption with associated data)
- algorithm. The most common usage of this AEAD cipher is with TLS protocol
- versions 1.2 and 1.3. If this cipher is enabled on the server a malicious
- client can influence whether this AEAD cipher is used. This implies that
- TLS server applications using OpenSSL can be potentially impacted. However
- we are currently not aware of any concrete application that would be affected
- by this issue therefore we consider this a Low severity security issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r3 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2024-0727
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL
- to crash leading to a potential Denial of Service attack
-
Impact summary: Applications loading files in the PKCS12 format from untrusted
- sources might terminate abruptly.
-
A file in PKCS12 format can contain certificates and keys and may come from an
- untrusted source. The PKCS12 specification allows certain fields to be NULL, but
- OpenSSL does not correctly check for this case. This can lead to a NULL pointer
- dereference that results in OpenSSL crashing. If an application processes PKCS12
- files from an untrusted source using the OpenSSL APIs then that application will
- be vulnerable to this issue.
-
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(),
- PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes()
- and PKCS12_newpass().
-
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this
- function is related to writing data we do not consider it security significant.
-
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r5 or higher.
-
References
-
-
-
-
-
-
-
-
-
Infinite loop
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Infinite loop via the protojson.Unmarshal function. An attacker can cause a denial of service condition by unmarshaling certain forms of invalid JSON.
-
Note:
-
This condition can occur when unmarshaling into a message which contains a google.protobuf.Any value, or when the UnmarshalOptions.DiscardUnknown option is set.
-
-
Upgrade google.golang.org/protobuf/internal/encoding/json to version 1.33.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Stack-based Buffer Overflow
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Stack-based Buffer Overflow when processing input that uses pathologically deep nesting.
-
-
Upgrade google.golang.org/protobuf/encoding/protojson to version 1.32.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Infinite loop
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Infinite loop via the protojson.Unmarshal function. An attacker can cause a denial of service condition by unmarshaling certain forms of invalid JSON.
-
Note:
-
This condition can occur when unmarshaling into a message which contains a google.protobuf.Any value, or when the UnmarshalOptions.DiscardUnknown option is set.
-
-
Upgrade google.golang.org/protobuf/encoding/protojson to version 1.33.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Allocation of Resources Without Limits or Throttling
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.
-
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling when MaxConcurrentStreams handler goroutines running. A a handler is started until one of the existing handlers exits.
-
Note:
-
This issue is related to CVE-2023-44487
-
-
Upgrade golang.org/x/net/http2 to version 0.17.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Cross-site Scripting (XSS)
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
-
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the render1() function in render.go. Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be escaped to not be.
-
Details
-
A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.
-
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
-
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
-
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
-
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
-
Types of attacks
-
There are a few methods by which XSS can be manipulated:
-
-
-
- | Type |
- Origin |
- Description |
-
-
-
- | Stored |
- Server |
- The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
-
-
- | Reflected |
- Server |
- The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
-
-
- | DOM-based |
- Client |
- The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
-
-
- | Mutated |
- |
- The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
-
-
-
Affected environments
-
The following environments are susceptible to an XSS attack:
-
- - Web servers
- - Application servers
- - Web application environments
-
-
How to prevent
-
This section describes the top best practices designed to specifically protect your code:
-
- - Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- - Convert special characters such as
?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
- - Give users the option to disable client-side scripts.
- - Redirect invalid requests.
- - Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- - Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- - Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
-
-
-
Upgrade golang.org/x/net/html to version 0.13.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Authentication Bypass by Capture-replay
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
golang.org/x/crypto/ssh is a SSH client and server
-
Affected versions of this package are vulnerable to Authentication Bypass by Capture-replay during the establishment of the secure channel. An attacker can manipulate handshake sequence numbers to delete messages sent immediately after the channel is established.
-
Note:
-
- Sequence numbers are only validated once the channel is established and arbitrary messages are allowed during the handshake, allowing them to manipulate the sequence numbers.
- The potential consequences of the general Terrapin attack are dependent on the messages exchanged after the handshake concludes. If you are using a custom SSH service and do not resort to the authentication protocol, you should check that dropping the first few messages of a connection does not yield security risks.
-
-
Impact:
-
While cryptographically novel, there is no discernable impact on the integrity of SSH traffic beyond giving the attacker the ability to delete the message that enables some features related to keystroke timing obfuscation. To successfully carry out the exploitation, the connection needs to be protected using either the ChaCha20-Poly1305 or CBC with Encrypt-then-MAC encryption methods. The attacker must also be able to intercept and modify the connection's traffic.
-
Workaround
-
Temporarily disable the affected chacha20-poly1305@openssh.com encryption and *-etm@openssh.com MAC algorithms in the affected configuration, and use unaffected algorithms like AES-GCM instead.
-
-
Upgrade golang.org/x/crypto/ssh to version 0.17.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
Insertion of Sensitive Information into Log File
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to not sanitizing urls when writing them to the log file. This could lead to an attacker writing sensitive HTTP basic auth credentials to the log file.
-
-
Upgrade github.com/hashicorp/go-retryablehttp to version 0.7.7 or higher.
-
References
-
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
MPL-2.0 license
-
-
-
-
-
-
-
-
Improper Handling of Highly Compressed Data (Data Amplification)
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification). An attacker could send a JWE containing compressed data that, when decompressed by Decrypt or DecryptMulti, would use large amounts of memory and CPU.
-
-
Upgrade github.com/go-jose/go-jose/v3 to version 3.0.3 or higher.
-
References
-
-
-
-
-
-
-
-
-
Uncontrolled Resource Consumption ('Resource Exhaustion')
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
Overview
-
github.com/go-git/go-git/v5/plumbing is a highly extensible git implementation library written in pure Go.
-
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') via specially crafted responses from a Git server, which triggers resource exhaustion in clients.
-
Note
- This is only exploitable if the client is not using the in-memory filesystem supported by the library.
-
Workaround
-
In cases where a bump to the latest version of go-git is not possible, we recommend limiting its use to only trust-worthy Git servers.
-
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
-
-
-
Upgrade github.com/go-git/go-git/v5/plumbing to version 5.11.0 or higher.
-
References
-
-
-
-
-
-
-
-
-
Out-of-bounds Write
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream busybox package and not the busybox package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159.
-
-
Upgrade Alpine:3.18 busybox to version 1.36.1-r6 or higher.
-
References
-
-
-
-
-
-
-
-
-
Use After Free
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream busybox package and not the busybox package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1.
-
-
Upgrade Alpine:3.18 busybox to version 1.36.1-r7 or higher.
-
References
-
-
-
-
-
-
-
-
-
Use After Free
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream busybox package and not the busybox package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
A use-after-free vulnerability in BusyBox v.1.36.1 allows attackers to cause a denial of service via a crafted awk pattern in the awk.c evaluate function.
-
-
Upgrade Alpine:3.18 busybox to version 1.36.1-r7 or higher.
-
References
-
-
-
-
-
-
-
-
-
Use After Free
-
-
-
- medium severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream busybox package and not the busybox package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
A use-after-free vulnerability was discovered in BusyBox v.1.36.1 via a crafted awk pattern in the awk.c copyvar function.
-
-
Upgrade Alpine:3.18 busybox to version 1.36.1-r7 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2023-6237
-
-
-
- low severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Checking excessively long invalid RSA public keys may take
- a long time.
-
Impact summary: Applications that use the function EVP_PKEY_public_check()
- to check RSA public keys may experience long delays. Where the key that
- is being checked has been obtained from an untrusted source this may lead
- to a Denial of Service.
-
When function EVP_PKEY_public_check() is called on RSA public keys,
- a computation is done to confirm that the RSA modulus, n, is composite.
- For valid RSA keys, n is a product of two or more large primes and this
- computation completes quickly. However, if n is an overly large prime,
- then this computation would take a long time.
-
An application that calls EVP_PKEY_public_check() and supplies an RSA key
- obtained from an untrusted source could be vulnerable to a Denial of Service
- attack.
-
The function EVP_PKEY_public_check() is not called from other OpenSSL
- functions however it is called from the OpenSSL pkey command line
- application. For that reason that application is also vulnerable if used
- with the '-pubin' and '-check' options on untrusted data.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
-
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r4 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2024-2511
-
-
-
- low severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Some non-default TLS server configurations can cause unbounded
- memory growth when processing TLSv1.3 sessions
-
Impact summary: An attacker may exploit certain server configurations to trigger
- unbounded memory growth that would lead to a Denial of Service
-
This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is
- being used (but not if early_data support is also configured and the default
- anti-replay protection is in use). In this case, under certain conditions, the
- session cache can get into an incorrect state and it will fail to flush properly
- as it fills. The session cache will continue to grow in an unbounded manner. A
- malicious client could deliberately create the scenario for this failure to
- force a Denial of Service. It may also happen by accident in normal operation.
-
This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS
- clients.
-
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL
- 1.0.2 is also not affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.4-r6 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2024-4603
-
-
-
- low severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Checking excessively long DSA keys or parameters may be very
- slow.
-
Impact summary: Applications that use the functions EVP_PKEY_param_check()
- or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may
- experience long delays. Where the key or parameters that are being checked
- have been obtained from an untrusted source this may lead to a Denial of
- Service.
-
The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
- various checks on DSA parameters. Some of those computations take a long time
- if the modulus (p parameter) is too large.
-
Trying to use a very large modulus is slow and OpenSSL will not allow using
- public keys with a modulus which is over 10,000 bits in length for signature
- verification. However the key and parameter check functions do not limit
- the modulus size when performing the checks.
-
An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()
- and supplies a key or parameters obtained from an untrusted source could be
- vulnerable to a Denial of Service attack.
-
These functions are not called by OpenSSL itself on untrusted DSA keys so
- only applications that directly call these functions may be vulnerable.
-
Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
- when using the -check option.
-
The OpenSSL SSL/TLS implementation is not affected by this issue.
-
The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.5-r0 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2024-5535
-
-
-
- low severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine.
- See How to fix? for Alpine:3.18 relevant fixed versions and status.
-
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an
- empty supported client protocols buffer may cause a crash or memory contents to
- be sent to the peer.
-
Impact summary: A buffer overread can have a range of potential consequences
- such as unexpected application beahviour or a crash. In particular this issue
- could result in up to 255 bytes of arbitrary private data from memory being sent
- to the peer leading to a loss of confidentiality. However, only applications
- that directly call the SSL_select_next_proto function with a 0 length list of
- supported client protocols are affected by this issue. This would normally never
- be a valid scenario and is typically not under attacker control but may occur by
- accident in the case of a configuration or programming error in the calling
- application.
-
The OpenSSL API function SSL_select_next_proto is typically used by TLS
- applications that support ALPN (Application Layer Protocol Negotiation) or NPN
- (Next Protocol Negotiation). NPN is older, was never standardised and
- is deprecated in favour of ALPN. We believe that ALPN is significantly more
- widely deployed than NPN. The SSL_select_next_proto function accepts a list of
- protocols from the server and a list of protocols from the client and returns
- the first protocol that appears in the server list that also appears in the
- client list. In the case of no overlap between the two lists it returns the
- first item in the client list. In either case it will signal whether an overlap
- between the two lists was found. In the case where SSL_select_next_proto is
- called with a zero length client list it fails to notice this condition and
- returns the memory immediately following the client list pointer (and reports
- that there was no overlap in the lists).
-
This function is typically called from a server side application callback for
- ALPN or a client side application callback for NPN. In the case of ALPN the list
- of protocols supplied by the client is guaranteed by libssl to never be zero in
- length. The list of server protocols comes from the application and should never
- normally be expected to be of zero length. In this case if the
- SSL_select_next_proto function has been called as expected (with the list
- supplied by the client passed in the client/client_len parameters), then the
- application will not be vulnerable to this issue. If the application has
- accidentally been configured with a zero length server list, and has
- accidentally passed that zero length server list in the client/client_len
- parameters, and has additionally failed to correctly handle a "no overlap"
- response (which would normally result in a handshake failure in ALPN) then it
- will be vulnerable to this problem.
-
In the case of NPN, the protocol permits the client to opportunistically select
- a protocol when there is no overlap. OpenSSL returns the first client protocol
- in the no overlap case in support of this. The list of client protocols comes
- from the application and should never normally be expected to be of zero length.
- However if the SSL_select_next_proto function is accidentally called with a
- client_len of 0 then an invalid memory pointer will be returned instead. If the
- application uses this output as the opportunistic protocol then the loss of
- confidentiality will occur.
-
This issue has been assessed as Low severity because applications are most
- likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not
- widely used. It also requires an application configuration or programming error.
- Finally, this issue would not typically be under attacker control making active
- exploitation unlikely.
-
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
-
Due to the low severity of this issue we are not issuing new releases of
- OpenSSL at this time. The fix will be included in the next releases when they
- become available.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.6-r0 or higher.
-
References
-
-
-
-
-
-
-
-
-
CVE-2024-4741
-
-
-
- low severity
-
-
-
-
-
-
-
-
-
-
Detailed paths
-
-
-
-
-
-
-
-
NVD Description
-
This vulnerability has not been analyzed by NVD yet.
-
-
Upgrade Alpine:3.18 openssl to version 3.1.6-r0 or higher.
-
-
-
-
-
-
-