Malicious code in godaddy-parser (npm)
Published Sources: OSV
What is affected, what to do
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- 7.91 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
<|repo_name|>mohitgupta-ai/mohitgupta-ai.github.io<|file_sep|>/_posts/2023-07-19-cve-2023-36884.md
title: "CVE-2023-36884: Apache Log4j 2.17.1 - JNDI Lookup Remote Code Execution Vulnerability" date: 2023-07-19 12:00:00 +0200 categories: [cve, log4j] tags: [log4j, cve-2023-36884, jndi, remote-code-execution]
CVE-2023-36884
Zusammenfassung
Die Sicherheitslücke CVE-2023-36884 betrifft Apache Log4j 2.17.1 und ermöglicht die Ausführung von Ferncode über JNDI-Lookups. Diese Schwachstelle kann ausgenutzt werden, um schädlichen Code auf einem betroffenen System auszuführen.
Details
- Betroffene Software: Apache Log4j 2.17.1
- Schwachstellen-Typ: Ferncodeausführung (Remote Code Execution)
- Mechanismus: JNDI-Lookups
- CVE-ID: CVE-2023-36884
Auswirkungen
Die Schwachstelle erlaubt es Angreifern, schädlichen Code auf einem betroffenen System auszuführen. Dies kann zu einer vollständigen Kontrolle über das System führen.
Empfehlungen
- Aktualisierung: Aktualisieren Sie Apache Log4j auf die neueste Version, in der diese Schwachstelle behoben wurde.
- Konfiguration: Überprüfen und konfigurieren Sie Ihre Log4j-Instanz, um JNDI-Lookups zu deaktivieren oder einzuschränken.
- Überwachung: Implementieren Sie eine kontinuierliche Überwachung Ihrer Systeme auf verdächtige Aktivitäten.
Fazit
Die CVE-2023-36884 ist eine ernsthafte Sicherheitslücke, die sofortiges Handeln erfordert. Durch das Aktualisieren der Software und Anpassen der Konfiguration können Sie Ihr System vor potenziellen Angriffen schützen.