Ubuntu Security Notice 7097-1 - Andy Boothe discovered that the Networking component of OpenJDK 11 did not properly handle access under certain circumstances. An unauthenticated attacker could possibly use this issue to cause a denial of service. It was discovered that the Hotspot component of OpenJDK 11 did not properly handle vectorization under certain circumstances. An unauthenticated attacker could possibly use this issue to access unauthorized resources and expose sensitive information.

==========================================================================  
Ubuntu Security Notice USN-7097-1  
November 11, 2024

openjdk-lts vulnerabilities  
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 24.10  
- Ubuntu 24.04 LTS  
- Ubuntu 22.04 LTS  
- Ubuntu 20.04 LTS  
- Ubuntu 18.04 LTS

Summary:

Several security issues were fixed in OpenJDK 11.

Software Description:  
- openjdk-lts: Open Source Java implementation

Details:

Andy Boothe discovered that the Networking component of OpenJDK 11 did not  
properly handle access under certain circumstances. An unauthenticated  
attacker could possibly use this issue to cause a denial of service.  
(CVE-2024-21208)

It was discovered that the Hotspot component of OpenJDK 11 did not properly  
handle vectorization under certain circumstances. An unauthenticated  
attacker could possibly use this issue to access unauthorized resources  
and expose sensitive information. (CVE-2024-21210, CVE-2024-21235)

It was discovered that the Serialization component of OpenJDK 11 did not  
properly handle deserialization under certain circumstances. An  
unauthenticated attacker could possibly use this issue to cause a denial  
of service. (CVE-2024-21217)

It was discovered that the Hotspot component of OpenJDK 11 was not properly  
bounding certain UTF-8 strings, which could lead to a buffer overflow. An  
attacker could possibly use this issue to cause a denial of service or  
execute arbitrary code. This issue was only addressed in Ubuntu 18.04 LTS.  
(CVE-2024-21131)

It was discovered that the Hotspot component of OpenJDK 11 could be made to  
run into an infinite loop. If an automated system were tricked into  
processing excessively large symbols, an attacker could possibly use this  
issue to cause a denial of service. This issue was only addressed in Ubuntu  
18.04 LTS. (CVE-2024-21138)

It was discovered that the Hotspot component of OpenJDK 11 did not properly  
perform range check elimination. An attacker could possibly use this issue  
to cause a denial of service, execute arbitrary code or bypass Java  
sandbox restrictions. This issue was only addressed in Ubuntu 18.04 LTS.  
(CVE-2024-21140)

Yakov Shafranovich discovered that the Concurrency component of OpenJDK 11  
incorrectly performed header validation in the Pack200 archive format. An  
attacker could possibly use this issue to cause a denial of service. This  
issue was only addressed in Ubuntu 18.04 LTS. (CVE-2024-21144)

Sergey Bylokhov discovered that OpenJDK 11 did not properly manage memory  
when handling 2D images. An attacker could possibly use this issue to  
obtain sensitive information. This issue was only addressed in Ubuntu  
18.04 LTS. (CVE-2024-21145)

It was discovered that the Hotspot component of OpenJDK 11 incorrectly  
handled memory when performing range check elimination under certain  
circumstances. An attacker could possibly use this issue to cause a  
denial of service, execute arbitrary code or bypass Java sandbox  
restrictions. This issue was only addressed in Ubuntu 18.04 LTS.  
(CVE-2024-21147)

Update instructions:

The problem can be corrected by updating your system to the following  
package versions:

Ubuntu 24.10  
  openjdk-11-jdk                  11.0.25+9-1ubuntu1~24.10  
  openjdk-11-jdk-headless         11.0.25+9-1ubuntu1~24.10  
  openjdk-11-jre                  11.0.25+9-1ubuntu1~24.10  
  openjdk-11-jre-headless         11.0.25+9-1ubuntu1~24.10  
  openjdk-11-jre-zero             11.0.25+9-1ubuntu1~24.10

Ubuntu 24.04 LTS  
  openjdk-11-jdk                  11.0.25+9-1ubuntu1~24.04  
  openjdk-11-jdk-headless         11.0.25+9-1ubuntu1~24.04  
  openjdk-11-jre                  11.0.25+9-1ubuntu1~24.04  
  openjdk-11-jre-headless         11.0.25+9-1ubuntu1~24.04  
  openjdk-11-jre-zero             11.0.25+9-1ubuntu1~24.04

Ubuntu 22.04 LTS  
  openjdk-11-jdk                  11.0.25+9-1ubuntu1~22.04  
  openjdk-11-jdk-headless         11.0.25+9-1ubuntu1~22.04  
  openjdk-11-jre                  11.0.25+9-1ubuntu1~22.04  
  openjdk-11-jre-headless         11.0.25+9-1ubuntu1~22.04  
  openjdk-11-jre-zero             11.0.25+9-1ubuntu1~22.04

Ubuntu 20.04 LTS  
  openjdk-11-jdk                  11.0.25+9-1ubuntu1~20.04  
  openjdk-11-jdk-headless         11.0.25+9-1ubuntu1~20.04  
  openjdk-11-jre                  11.0.25+9-1ubuntu1~20.04  
  openjdk-11-jre-headless         11.0.25+9-1ubuntu1~20.04  
  openjdk-11-jre-zero             11.0.25+9-1ubuntu1~20.04

Ubuntu 18.04 LTS  
  openjdk-11-jdk                  11.0.25+9-1ubuntu1~18.04  
                                  Available with Ubuntu Pro  
  openjdk-11-jdk-headless         11.0.25+9-1ubuntu1~18.04  
                                  Available with Ubuntu Pro  
  openjdk-11-jre                  11.0.25+9-1ubuntu1~18.04  
                                  Available with Ubuntu Pro  
  openjdk-11-jre-headless         11.0.25+9-1ubuntu1~18.04  
                                  Available with Ubuntu Pro  
  openjdk-11-jre-zero             11.0.25+9-1ubuntu1~18.04  
                                  Available with Ubuntu Pro

This update uses a new upstream release, which includes additional bug  
fixes. After a standard system update you need to restart Java  
applications to make all the necessary changes.

References:  
  https://ubuntu.com/security/notices/USN-7097-1  
  CVE-2024-21131, CVE-2024-21138, CVE-2024-21140, CVE-2024-21144,  
  CVE-2024-21145, CVE-2024-21147, CVE-2024-21208, CVE-2024-21210,  
  CVE-2024-21217, CVE-2024-21235

Package Information:  
https://launchpad.net/ubuntu/+source/openjdk-lts/11.0.25+9-1ubuntu1~24.10  
https://launchpad.net/ubuntu/+source/openjdk-lts/11.0.25+9-1ubuntu1~24.04  
https://launchpad.net/ubuntu/+source/openjdk-lts/11.0.25+9-1ubuntu1~22.04  
https://launchpad.net/ubuntu/+source/openjdk-lts/11.0.25+9-1ubuntu1~20.04

Ubuntu Security Notice USN-7097-1

Ubuntu Security Notice 7096-1 - Andy Boothe discovered that the Networking component of OpenJDK 8 did not properly handle access under certain circumstances. An unauthenticated attacker could possibly use this issue to cause a denial of service. It was discovered that the Hotspot component of OpenJDK 8 did not properly handle vectorization under certain circumstances. An unauthenticated attacker could possibly use this issue to access unauthorized resources and expose sensitive information.

==========================================================================  
Ubuntu Security Notice USN-7096-1  
November 11, 2024

openjdk-8 vulnerabilities  
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 24.10  
- Ubuntu 24.04 LTS  
- Ubuntu 22.04 LTS  
- Ubuntu 20.04 LTS  
- Ubuntu 18.04 LTS  
- Ubuntu 16.04 LTS

Summary:

Several security issues were fixed in OpenJDK 8.

Software Description:  
- openjdk-8: Open Source Java implementation

Details:

Andy Boothe discovered that the Networking component of OpenJDK 8 did not  
properly handle access under certain circumstances. An unauthenticated  
attacker could possibly use this issue to cause a denial of service.  
(CVE-2024-21208)

It was discovered that the Hotspot component of OpenJDK 8 did not properly  
handle vectorization under certain circumstances. An unauthenticated  
attacker could possibly use this issue to access unauthorized resources  
and expose sensitive information. (CVE-2024-21210, CVE-2024-21235)

It was discovered that the Serialization component of OpenJDK 8 did not  
properly handle deserialization under certain circumstances. An  
unauthenticated attacker could possibly use this issue to cause a denial  
of service. (CVE-2024-21217)

It was discovered that the Hotspot component of OpenJDK 8 was not properly  
bounding certain UTF-8 strings, which could lead to a buffer overflow. An  
attacker could possibly use this issue to cause a denial of service or  
execute arbitrary code. This issue was only addressed in Ubuntu 16.04 LTS.  
(CVE-2024-21131)

It was discovered that the Hotspot component of OpenJDK 8 could be made to  
run into an infinite loop. If an automated system were tricked into  
processing excessively large symbols, an attacker could possibly use this  
issue to cause a denial of service. This issue was only addressed in Ubuntu  
16.04 LTS. (CVE-2024-21138)

It was discovered that the Hotspot component of OpenJDK 8 did not properly  
perform range check elimination. An attacker could possibly use this issue  
to cause a denial of service, execute arbitrary code or bypass Java  
sandbox restrictions. This issue was only addressed in Ubuntu 16.04 LTS.  
(CVE-2024-21140)

Yakov Shafranovich discovered that the Concurrency component of OpenJDK 8  
incorrectly performed header validation in the Pack200 archive format. An  
attacker could possibly use this issue to cause a denial of service. This  
issue was only addressed in Ubuntu 16.04 LTS. (CVE-2024-21144)

Sergey Bylokhov discovered that OpenJDK 8 did not properly manage memory  
when handling 2D images. An attacker could possibly use this issue to  
obtain sensitive information. This issue was only addressed in Ubuntu  
16.04 LTS. (CVE-2024-21145)

It was discovered that the Hotspot component of OpenJDK 8 incorrectly  
handled memory when performing range check elimination under certain  
circumstances. An attacker could possibly use this issue to cause a  
denial of service, execute arbitrary code or bypass Java sandbox  
restrictions. This issue was only addressed in Ubuntu 16.04 LTS.  
(CVE-2024-21147)

It was discovered that the Hotspot component of OpenJDK 8 incorrectly  
handled certain exceptions with specially crafted long messages. An  
attacker could possibly use this issue to cause a denial of service.  
This issue was only addressed in Ubuntu 16.04 LTS. (CVE-2024-21011)

Vladimir Kondratyev discovered that the Hotspot component of OpenJDK 8  
incorrectly handled address offset calculations in the C1 compiler. An  
attacker could possibly use this issue to cause a denial of service  
or execute arbitrary code. This issue was only addressed in Ubuntu  
16.04 LTS. (CVE-2024-21068)

Yakov Shafranovich discovered that OpenJDK 8 did not properly manage  
memory in the Pack200 archive format. An attacker could possibly use this  
issue to cause a denial of service. This issue was only addressed in Ubuntu  
16.04 LTS. (CVE-2024-21085)

It was discovered that the Hotspot component of OpenJDK 8 incorrectly  
handled array accesses in the C2 compiler. An attacker could possibly use  
this issue to cause a denial of service or execute arbitrary code. This  
issue was only addressed in Ubuntu 16.04 LTS. (CVE-2024-21094)

Yi Yang discovered that the Hotspot component of OpenJDK 8 incorrectly  
handled array accesses in the C1 compiler. An attacker could possibly  
use this issue to cause a denial of service, execute arbitrary code or  
bypass Java sandbox restrictions. This issue was only addressed in Ubuntu  
16.04 LTS. (CVE-2024-20918)

It was discovered that the Hotspot component of OpenJDK 8 did not  
properly verify bytecode in certain situations. An attacker could  
possibly use this issue to bypass Java sandbox restrictions. This  
issue was only addressed in Ubuntu 16.04 LTS. (CVE-2024-20919)

It was discovered that the Hotspot component of OpenJDK 8 had an  
optimization flaw when generating range check loop predicates. An attacker  
could possibly use this issue to cause a denial of service, execute  
arbitrary code or bypass Java sandbox restrictions. This issue was only  
addressed in Ubuntu 16.04 LTS. (CVE-2024-20921)

Valentin Eudeline discovered that OpenJDK 8 incorrectly handled certain  
options in the Nashorn JavaScript subcomponent. An attacker could  
possibly use this issue to execute arbitrary code. This issue was only  
addressed in Ubuntu 16.04 LTS. (CVE-2024-20926)

It was discovered that OpenJDK 8 could produce debug logs that contained  
private keys used for digital signatures. An attacker could possibly use  
this issue to obtain sensitive information. This issue was only addressed  
in Ubuntu 16.04 LTS. (CVE-2024-20945)

Hubert Kario discovered that the TLS implementation in OpenJDK 8 had a  
timing side-channel and incorrectly handled RSA padding. A remote attacker  
could possibly use this issue to recover sensitive information. This  
issue was only addressed in Ubuntu 16.04 LTS. (CVE-2024-20952)

Update instructions:

The problem can be corrected by updating your system to the following  
package versions:

Ubuntu 24.10  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~24.10  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~24.10  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~24.10  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~24.10  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~24.10

Ubuntu 24.04 LTS  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~24.04  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~24.04  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~24.04  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~24.04  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~24.04

Ubuntu 22.04 LTS  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~22.04  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~22.04  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~22.04  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~22.04  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~22.04

Ubuntu 20.04 LTS  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~20.04  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~20.04  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~20.04  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~20.04  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~20.04

Ubuntu 18.04 LTS  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~18.04  
                                  Available with Ubuntu Pro  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~18.04  
                                  Available with Ubuntu Pro  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~18.04  
                                  Available with Ubuntu Pro  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~18.04  
                                  Available with Ubuntu Pro  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~18.04  
                                  Available with Ubuntu Pro

Ubuntu 16.04 LTS  
  openjdk-8-jdk                   8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro  
  openjdk-8-jdk-headless          8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro  
  openjdk-8-jre                   8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro  
  openjdk-8-jre-headless          8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro  
  openjdk-8-jre-jamvm             8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro  
  openjdk-8-jre-zero              8u432-ga~us1-0ubuntu2~16.04.4  
                                  Available with Ubuntu Pro

This update uses a new upstream release, which includes additional bug  
fixes. After a standard system update you need to restart Java  
applications to make all the necessary changes.

References:  
  https://ubuntu.com/security/notices/USN-7096-1  
  CVE-2024-20918, CVE-2024-20919, CVE-2024-20921, CVE-2024-20926,  
  CVE-2024-20945, CVE-2024-20952, CVE-2024-21011, CVE-2024-21068,  
  CVE-2024-21085, CVE-2024-21094, CVE-2024-21131, CVE-2024-21138,  
  CVE-2024-21140, CVE-2024-21144, CVE-2024-21145, CVE-2024-21147,  
  CVE-2024-21208, CVE-2024-21210, CVE-2024-21217, CVE-2024-21235

Package Information:  
https://launchpad.net/ubuntu/+source/openjdk-8/8u432-ga~us1-0ubuntu2~24.10  
https://launchpad.net/ubuntu/+source/openjdk-8/8u432-ga~us1-0ubuntu2~24.04  
https://launchpad.net/ubuntu/+source/openjdk-8/8u432-ga~us1-0ubuntu2~22.04  
https://launchpad.net/ubuntu/+source/openjdk-8/8u432-ga~us1-0ubuntu2~20.04

Ubuntu Security Notice USN-7096-1

Red Hat Security Advisory 2024-8974-03 - Red Hat Advanced Cluster Management for Kubernetes 2.12.0 GA release images are now available, which contain security and bug fixes.

The following advisory data is extracted from:

https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8974.json

Red Hat officially shut down their mailing list notifications October 10, 2023.  Due to this, Packet Storm has recreated the below data as a reference point to raise awareness.  It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.

- Packet Storm Staff

====================================================================  
Red Hat Security Advisory

Synopsis:           Important: Red Hat Advanced Cluster Management 2.12.0 security and bug fixes  
Advisory ID:        RHSA-2024:8974-03  
Product:            Red Hat ACM  
Advisory URL:       https://access.redhat.com/errata/RHSA-2024:8974  
Issue date:         2024-11-11  
Revision:           03  
CVE Names:          CVE-2023-37788  
====================================================================

Summary: 

Red Hat Advanced Cluster Management for Kubernetes 2.12.0 GA release images are now available, which contain security and bug fixes.

Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE links in the References section.

Description:

Red Hat Advanced Cluster Management for Kubernetes 2.12.0 images

Red Hat Advanced Cluster Management for Kubernetes provides the  
capabilities to address common challenges that administrators and site  
reliability engineers face as they work across a range of public and  
private cloud environments. Clusters and applications are all visible and  
managed from a single console—with security policy built in.

This advisory contains the container images for Red Hat Advanced Cluster  
Management for Kubernetes, which fix several bugs. See the following  
Release Notes documentation, which will be updated shortly for this  
release, for additional details about this release:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/release_notes/

Security fix(es):

CVE-2024-48949 Missing Validation in Elliptic's EDDSA Signature Verification

Jira issues fixed: 

- ACM-11757: Managed clusters flip between Available and Degraded  
- ACM-12215: Provisioning OpenShift on OpenStack fails. The bootstrap node is failing to get the ignition image from Glance. Failing with tls: failed to verify certificate: x509: certificate signed by unknown authority.  
- ACM-12372: multicluster-observability-operator pod restarts with fatal error concurrent map writes  
- ACM-12738: Endpointmetrics does not reconcile CMO Config changes  
- ACM-13066: upgrade from a 2.10 that failed to update MCE to a 2.11 was possible  
- ACM-13149: cluster-monitoring-config retains old Hub for metrics forwarding after transfer to new Hub  
- ACM-14172: Observability pods should not inherit the defaultNodeSelector from the scheduler

Solution:

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/install/installing

CVEs:

CVE-2023-37788

References:

https://access.redhat.com/security/updates/classification/#important  
https://issues.redhat.com/browse/ACM-11757  
https://issues.redhat.com/browse/ACM-12215  
https://issues.redhat.com/browse/ACM-12372  
https://issues.redhat.com/browse/ACM-12738  
https://issues.redhat.com/browse/ACM-13066  
https://issues.redhat.com/browse/ACM-13149  
https://issues.redhat.com/browse/ACM-14172

Red Hat Security Advisory 2024-8974-03

A flaw was found in moodle. Insufficient sanitizing of data when performing a restore could result in a cross-site scripting (XSS) risk from malicious backup files.

**Exploitability Metrics**

Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.

Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.

Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.

Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.

User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.

**Vulnerable System Impact Metrics**

Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).

Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.

**Subsequent System Impact Metrics**

Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).

Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.

GHSA-4hjf-6pxr-549h: Moodle Cross-site Scripting vulnerability

A flaw was found in moodle. When creating an export of site administration presets, some sensitive secrets and keys are not being excluded from the export, which could result in them unintentionally being leaked if the presets are shared with a third party.

GHSA-vpq5-56jj-vf2m: Moodle admin presets export tool includes some secrets that should not be exported

A flaw was found in moodle. The cURL wrapper in Moodle strips HTTPAUTH and USERPWD headers during emulated redirects, but retains other original request headers, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.

GHSA-7wmp-2xmx-g6h8: Moodle authorization headers preserved between "emulated redirects"

A flaw was found in moodle. Some hidden user profile fields are visible in gradebook reports, which could result in users without the "view hidden user fields" capability having access to the information.

GHSA-c767-4whh-v7rw: Moodle has user information visibility control issues in gradebook reports

A flaw was found in moodle. Insufficient capability checks make it possible for users with access to restore glossaries in courses to restore them into the global site glossary.

GHSA-4gq2-x5w4-7hp8: Moodle has insufficient capability checks

A flaw was found in moodle. Matrix room membership and power levels are incorrectly applied and revoked for suspended Moodle users.

GHSA-q99x-mjmh-v8w7: Moodle's user/power level management inconsistent with suspended users

A flaw was found in moodle. External API access to Quiz can override contained insufficient access control.

Tag

#auth