SUSE SLED15: apiguardian / apiguardian-javadoc / assertj-core / byte-buddy / etc (SUSE-SU-2024:1874-1)

high Nessus Plugin ID 198282

Language:

Synopsis

The remote SUSE host is missing a security update.

Description

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2024:1874-1 advisory.

This update for Java fixes thefollowing issues:

apiguardian was updated to vesion 1.1.2:

- Added LICENSE/NOTICE to the generated jar
- Allow @API to be declared at the package level
- Explain usage of Status.DEPRECATED
- Include OSGi metadata in manifest

assertj-core was implemented at version 3.25.3:

- New package implementation needed by Junit5

byte-buddy was updated to version v1.14.16:

- `byte-buddy` is required by `assertj-core`
- Changes in version v1.14.16:

* Update ASM and introduce support for Java 23.

- Changes in version v1.14.15:

* Allow attaching from root on J9.

- Changes of v1.14.14:

* Adjust type validation to accept additional names that are legal in the class file format.
* Fix dynamic attach on Windows when a service user is active.
* Avoid failure when using Android's strict mode.

dom4j was updated to version 2.1.4:

- Improvements and potentially breaking changes:

* Added new factory method org.dom4j.io.SAXReader.createDefault(). It has more secure defaults than new SAXReader(), which uses system XMLReaderFactory.createXMLReader() or SAXParserFactory.newInstance().newSAXParser().
* If you use some optional dependency of dom4j (for example Jaxen, xsdlib etc.), you need to specify an explicit dependency on it in your project. They are no longer marked as a mandatory transitive dependency by dom4j.
* Following SAX parser features are disabled by default in DocumentHelper.parse() for security reasons (they were enabled in previous versions):

- http://xml.org/sax/properties/external-general-entities
- http://xml.org/sax/properties/external-parameter-entities


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Solution

Update the affected packages.

See Also

https://bugzilla.suse.com/1187446

https://bugzilla.suse.com/1224410

https://lists.suse.com/pipermail/sle-updates/2024-May/035436.html

https://www.suse.com/security/cve/CVE-2021-33813

Plugin Details

Severity: High

ID: 198282

File Name: suse_SU-2024-1874-1.nasl

Version: 1.3

Type: Local

Agent: unix

Published: 6/1/2024

Updated: 6/26/2026

Supported Sensors: Frictionless Assessment AWS, Frictionless Assessment Azure, Frictionless Assessment Agent, Nessus Agent, Agentless Assessment, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.7

CVSS v2

Risk Factor: Medium

Base Score: 5

Temporal Score: 3.9

Vector: CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:P

CVSS Score Source: CVE-2021-33813

CVSS v3

Risk Factor: High

Base Score: 7.5

Temporal Score: 6.7

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C

Vulnerability Information

CPE: p-cpe:/a:novell:suse_linux:jdom, p-cpe:/a:novell:suse_linux:byte-buddy, p-cpe:/a:novell:suse_linux:assertj-core, p-cpe:/a:novell:suse_linux:open-test-reporting-events, p-cpe:/a:novell:suse_linux:objectweb-asm, p-cpe:/a:novell:suse_linux:junit, p-cpe:/a:novell:suse_linux:junit5-minimal, p-cpe:/a:novell:suse_linux:dom4j, p-cpe:/a:novell:suse_linux:xom, p-cpe:/a:novell:suse_linux:hamcrest, p-cpe:/a:novell:suse_linux:jopt-simple, p-cpe:/a:novell:suse_linux:apiguardian, p-cpe:/a:novell:suse_linux:jaxen, p-cpe:/a:novell:suse_linux:open-test-reporting-schema, p-cpe:/a:novell:suse_linux:junit5, cpe:/o:novell:suse_linux:15

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/SuSE/release, Host/SuSE/rpm-list

Exploit Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 5/31/2024

Vulnerability Publication Date: 6/16/2021

Reference Information

CVE: CVE-2021-33813

SuSE: SUSE-SU-2024:1874-1