SBOM security assessment: Vulnerabilities affecting third-party components
Published Sources: NCSC NZ
What is affected, what to do
SBOM security assessment: Vulnerabilities affecting third-party components Multiple vulnerabilities have been discovered in a series of Java-based projects, some of which could allow an attacker to bypass authentication, read arbitrary files or access sensitive information. Please note that the vulnerabilities affect components in older versions of projects which may have been changed, updated or deleted since.
The available sources name no fixed version. Check the vendor guidance and the linked original advisory.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
XIEM Effective CVSS
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
SBOM security assessment: Vulnerabilities affecting third-party components Multiple vulnerabilities have been discovered in a series of Java-based projects, some of which could allow an attacker to bypass authentication, read arbitrary files or access sensitive information. Please note that the vulnerabilities affect components in older versions of projects which may have been changed, updated or deleted since. Organisations should assess potentially affected systems and apply vendor-provided patches as soon as possible. What's happening Systems affected Apache Kerby: Allows an attacker to impersonate any user, including administrators, by obtaining valid Kerberos authentication tickets. Affected Versions: Apache Kerby 1.0.0 to 2.0.x (fixed in 2.1.0) MockServer: Allows unauthenticated attackers to read files and access internal systems through XML processing and server-side request forgery (SSRF). Affected Versions: MockServer 5.5.4 and later; partial fix introduced in 6.0.0 Javassist: An exposed Javassist Webserver can allow attackers to read arbitrary files from the underlying host system. Affected Versions: Javassist 3.13.0-GA to 3.31.x (fixed in 3.32.0-GA) SAAJ (SOAP Parser): Malicious SOAP messages may allow file disclosure, internal network access, or denial-of-service in specific configurations. Affected Versions: All versions prior to 3.0.0 JJWT Signature Validation Bypass: Under certain implementation conditions, applications may accept forged JWT authentication tokens without validating the signature. Affected Versions: All versions prior to 0.12.0 WireMock Arbitrary File Delete: An unauthenticated attacker may be able to delete files on Windows systems running exposed WireMock instances. Affected Versions: WireMock 2.14.0 to 2.x (fixed in 3.0.0-beta-1) JJWT Denial of Service: Specially crafted JWTs can exhaust memory and cause application outages. Affected Versions: JJWT 0.6.0 to 0.11.x (fixed in 0.12.0) Google libphonenumber: Malicious input can consume excessive CPU resources and potentially disrupt application availability. Affected Versions: libphonenumber 3.1 to 9.0.35 (fixed in 9.0.36) Javassist Resource Exhaustion: Repeated malformed requests can exhaust system resources and cause service disruption. Affected Versions: Javassist 3.13.0-GA to 3.31.x (fixed in 3.32.0-GA) WireMock Path Traversal: An attacker may gain limited access to files outside WireMock's intended storage directory. Affected Versions: WireMock 2.16.0 to 2.x (fixed in 3.0.0-beta-1) Auth0 Java JWT: Malformed authentication tokens can trigger application exceptions and potentially impact service availability. Affected Versions: java-jwt 3.0.1 to 3.19.1 (fixed in 3.19.2) Apache Qpid Broker-J: Authentication timing differences could theoretically assist password recovery, although exploitation is difficult in practice. Affected Versions : Qpid Broker-J 0.26 to 9.x (fixed in 10.0.0) What to do Prevention Upgrade to a supported, non-vulnerable version where available, or remove the affected component if no fixed version exists. More information Identify potentially affected products within your environment and refer to the guidance provided by the maintainers of each codebase for remediation requirements.