golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Note:Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
+
When asked to both use a .netrc file for credentials and to follow HTTP
+ redirects, curl could leak the password used for the first host to the
+ followed-to host under certain circumstances.
+
This flaw only manifests itself if the netrc file has an entry that matches
+ the redirect target hostname but the entry either omits just the password or
+ omits both login and password.
+
Remediation
+
Upgrade Ubuntu:22.04curl to version 7.81.0-1ubuntu1.20 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Note:Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
When asked to both use a .netrc file for credentials and to follow HTTP
+ redirects, curl could leak the password used for the first host to the
+ followed-to host under certain circumstances.
+
This flaw only manifests itself if the netrc file has an entry that matches
+ the redirect target hostname but the entry either omits just the password or
+ omits both login and password.
+
Remediation
+
Upgrade Ubuntu:24.04curl to version 8.5.0-2ubuntu10.6 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Note:Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
When asked to both use a .netrc file for credentials and to follow HTTP
+ redirects, curl could leak the password used for the first host to the
+ followed-to host under certain circumstances.
+
This flaw only manifests itself if the netrc file has an entry that matches
+ the redirect target hostname but the entry either omits just the password or
+ omits both login and password.
+
Remediation
+
Upgrade Ubuntu:24.04curl to version 8.5.0-2ubuntu10.6 or higher.
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
+
+
Remediation
+
Add `resources.limits.cpu` field with required CPU limit value
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass
+
+
Remediation
+
Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient backtracking in the regular expressions used in URL forms.
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.
+
Let’s take the following regular expression as an example:
+
regex = /A(B|C+)+D/
+
+
This regular expression accomplishes the following:
+
+
A The string must start with the letter 'A'
+
(B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
+
D Finally, we ensure this section of the string ends with a 'D'
+
+
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
+
It most cases, it doesn't take very long for a regex engine to find a match:
+
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
+ 0.04s user 0.01s system 95% cpu 0.052 total
+
+ $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
+ 1.79s user 0.02s system 99% cpu 1.812 total
+
+
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
+
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
+
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
+
+
CCC
+
CC+C
+
C+CC
+
C+C+C.
+
+
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
+
From there, the number of steps the engine must use to validate a string just continues to grow.
+
+
+
+
String
+
Number of C's
+
Number of steps
+
+
+
+
ACCCX
+
3
+
38
+
+
+
ACCCCX
+
4
+
71
+
+
+
ACCCCCX
+
5
+
136
+
+
+
ACCCCCCCCCCCCCCX
+
14
+
65,553
+
+
+
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Affected versions of this package are vulnerable to Incorrect Implementation of Authentication Algorithm when the key passed in the last call before a connection is established is assumed to be the key used for authentication. It is not necessarily the authentication key in use, and this allows attackers who can control the key cache by making their own carefully-timed connections to bypass authorization with subsequent legitimate ServerConfig.PublicKeyCallback callbacks.
+
Note: The assumed caching behavior of this callback is not documented and is therefore considered human error, but the project maintainers have observed reliance on it for authorization decisions in production. In fact, the assumption is negated in the documentation, which states "A call to this function does not guarantee that the key offered is in fact used to authenticate." The behavior after upgrading still allows the possibility of an attacker forcing their own key to be the one in the cache when the callback is invoked if the client is using a different authentication method such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. It is therefore recommended to rely on the return values of the connection itself, found in ServerConn.Permissions for further authorization steps.
+
Remediation
+
Upgrade golang.org/x/crypto/ssh to version 0.31.0 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the form of gRPC metadata. If the metadata contains sensitive information an attacker can expose it.
+
Remediation
+
Upgrade google.golang.org/grpc/metadata to version 1.64.1 or higher.
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.20 relevant fixed versions and status.
+
Issue summary: Applications performing certificate name checks (e.g., TLS
+ clients checking server certificates) may attempt to read an invalid memory
+ address resulting in abnormal termination of the application process.
+
Impact summary: Abnormal termination of an application can a cause a denial of
+ service.
+
Applications performing certificate name checks (e.g., TLS clients checking
+ server certificates) may attempt to read an invalid memory address when
+ comparing the expected name with an otherName subject alternative name of an
+ X.509 certificate. This may result in an exception that terminates the
+ application program.
+
Note that basic certificate chain validation (signatures, dates, ...) is not
+ affected, the denial of service can occur only when the application also
+ specifies an expected DNS name, Email address or IP address.
+
TLS servers rarely solicit client certificates, and even when they do, they
+ generally don't perform a name check against a reference identifier (expected
+ identity), but rather extract the presented identity after checking the
+ certificate chain. So TLS servers are generally not affected and the severity
+ of the issue is Moderate.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-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.
+ See How to fix? for Alpine:3.20 relevant fixed versions and status.
+
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
+ explicit values for the field polynomial can lead to out-of-bounds memory reads
+ or writes.
+
Impact summary: Out of bound memory writes can lead to an application crash or
+ even a possibility of a remote code execution, however, in all the protocols
+ involving Elliptic Curve Cryptography that we're aware of, either only "named
+ curves" are supported, or, if explicit curve parameters are supported, they
+ specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
+ problematic input values. Thus the likelihood of existence of a vulnerable
+ application is low.
+
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
+ so problematic inputs cannot occur in the context of processing X.509
+ certificates. Any problematic use-cases would have to be using an "exotic"
+ curve encoding.
+
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
+ and various supporting BN_GF2m_*() functions.
+
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
+ that make it possible to represent invalid field polynomials with a zero
+ constant term, via the above or similar APIs, may terminate abruptly as a
+ result of reading or writing outside of array bounds. Remote code execution
+ cannot easily be ruled out.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-r1 or higher.
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.20 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.
+
Remediation
+
Upgrade Alpine:3.20busybox to version 1.36.1-r29 or higher.
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.20 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.
+
Remediation
+
Upgrade Alpine:3.20busybox to version 1.36.1-r29 or higher.
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.20 relevant fixed versions and status.
+
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause
+ memory to be accessed that was previously freed in some situations
+
Impact summary: A use after free can have a range of potential consequences such
+ as the corruption of valid data, crashes or execution of arbitrary code.
+ However, only applications that directly call the SSL_free_buffers function are
+ affected by this issue. Applications that do not call this function are not
+ vulnerable. Our investigations indicate that this function is rarely used by
+ applications.
+
The SSL_free_buffers function is used to free the internal OpenSSL buffer used
+ when processing an incoming record from the network. The call is only expected
+ to succeed if the buffer is not currently in use. However, two scenarios have
+ been identified where the buffer is freed even when still in use.
+
The first scenario occurs where a record header has been received from the
+ network and processed by OpenSSL, but the full record body has not yet arrived.
+ In this case calling SSL_free_buffers will succeed even though a record has only
+ been partially processed and the buffer is still in use.
+
The second scenario occurs where a full record containing application data has
+ been received and processed by OpenSSL but the application has only read part of
+ this data. Again a call to SSL_free_buffers will succeed even though the buffer
+ is still in use.
+
While these scenarios could occur accidentally during normal operation a
+ malicious attacker could attempt to engineer a stituation where this occurs.
+ We are not aware of this issue being actively exploited.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.0-r3 or higher.
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.20 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.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.1-r1 or higher.
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.20 relevant fixed versions and status.
+
Issue summary: Applications performing certificate name checks (e.g., TLS
+ clients checking server certificates) may attempt to read an invalid memory
+ address resulting in abnormal termination of the application process.
+
Impact summary: Abnormal termination of an application can a cause a denial of
+ service.
+
Applications performing certificate name checks (e.g., TLS clients checking
+ server certificates) may attempt to read an invalid memory address when
+ comparing the expected name with an otherName subject alternative name of an
+ X.509 certificate. This may result in an exception that terminates the
+ application program.
+
Note that basic certificate chain validation (signatures, dates, ...) is not
+ affected, the denial of service can occur only when the application also
+ specifies an expected DNS name, Email address or IP address.
+
TLS servers rarely solicit client certificates, and even when they do, they
+ generally don't perform a name check against a reference identifier (expected
+ identity), but rather extract the presented identity after checking the
+ certificate chain. So TLS servers are generally not affected and the severity
+ of the issue is Moderate.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-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.
+ See How to fix? for Alpine:3.20 relevant fixed versions and status.
+
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
+ explicit values for the field polynomial can lead to out-of-bounds memory reads
+ or writes.
+
Impact summary: Out of bound memory writes can lead to an application crash or
+ even a possibility of a remote code execution, however, in all the protocols
+ involving Elliptic Curve Cryptography that we're aware of, either only "named
+ curves" are supported, or, if explicit curve parameters are supported, they
+ specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
+ problematic input values. Thus the likelihood of existence of a vulnerable
+ application is low.
+
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
+ so problematic inputs cannot occur in the context of processing X.509
+ certificates. Any problematic use-cases would have to be using an "exotic"
+ curve encoding.
+
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
+ and various supporting BN_GF2m_*() functions.
+
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
+ that make it possible to represent invalid field polynomials with a zero
+ constant term, via the above or similar APIs, may terminate abruptly as a
+ result of reading or writing outside of array bounds. Remote code execution
+ cannot easily be ruled out.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-r1 or higher.
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.20 relevant fixed versions and status.
+
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
+ explicit values for the field polynomial can lead to out-of-bounds memory reads
+ or writes.
+
Impact summary: Out of bound memory writes can lead to an application crash or
+ even a possibility of a remote code execution, however, in all the protocols
+ involving Elliptic Curve Cryptography that we're aware of, either only "named
+ curves" are supported, or, if explicit curve parameters are supported, they
+ specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
+ problematic input values. Thus the likelihood of existence of a vulnerable
+ application is low.
+
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
+ so problematic inputs cannot occur in the context of processing X.509
+ certificates. Any problematic use-cases would have to be using an "exotic"
+ curve encoding.
+
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
+ and various supporting BN_GF2m_*() functions.
+
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
+ that make it possible to represent invalid field polynomials with a zero
+ constant term, via the above or similar APIs, may terminate abruptly as a
+ result of reading or writing outside of array bounds. Remote code execution
+ cannot easily be ruled out.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-r1 or higher.
golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.
+
Affected versions of this package are vulnerable to Denial of Service (DoS) through the functions parseDoctype, htmlIntegrationPoint, inBodyIM and inTableIM due to inefficient usage of the method strings.ToLower combining with the == operator to convert strings to lowercase and then comparing them.
+
An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.
+
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/html to version 0.33.0 or higher.
Note:Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.
Note:Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.
Note:Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.
Note:Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.
Note:Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.
Note:Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
+
Remediation
+
There is no fixed version for Ubuntu:24.04openssl.
Note:Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
+
Remediation
+
There is no fixed version for Ubuntu:24.04libgcrypt20.
Note:Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
Note:Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
Note:Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Note:Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.
Note:Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).
Note:Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Ubuntu.
+ See How to fix? for Ubuntu:24.04 relevant fixed versions and status.
+
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
+
Remediation
+
There is no fixed version for Ubuntu:24.04coreutils.
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.20 relevant fixed versions and status.
+
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
+ explicit values for the field polynomial can lead to out-of-bounds memory reads
+ or writes.
+
Impact summary: Out of bound memory writes can lead to an application crash or
+ even a possibility of a remote code execution, however, in all the protocols
+ involving Elliptic Curve Cryptography that we're aware of, either only "named
+ curves" are supported, or, if explicit curve parameters are supported, they
+ specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
+ problematic input values. Thus the likelihood of existence of a vulnerable
+ application is low.
+
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
+ so problematic inputs cannot occur in the context of processing X.509
+ certificates. Any problematic use-cases would have to be using an "exotic"
+ curve encoding.
+
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
+ and various supporting BN_GF2m_*() functions.
+
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
+ that make it possible to represent invalid field polynomials with a zero
+ constant term, via the above or similar APIs, may terminate abruptly as a
+ result of reading or writing outside of array bounds. Remote code execution
+ cannot easily be ruled out.
+
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
+
Remediation
+
Upgrade Alpine:3.20openssl to version 3.3.2-r1 or higher.