What is the CVSS score of CVE-2013-4378?

CVE-2013-4378 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.5%.

Is there a public PoC exploit available for CVE-2013-4378?

Yes, a public proof-of-concept exploit is available for CVE-2013-4378. Prioritise patching immediately. EPSS: 0.5%.

Is there a patch available for CVE-2013-4378?

Yes, a patch is available for CVE-2013-4378. Update the affected software to the latest version immediately.

Java CVE-2013-4378

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2013-09-30 secalert@redhat.com

Java XSS Javamelody

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:M/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Sep 30, 2013 - 22:55 cve.org

MEDIUM 4.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

3 maven packages depend on net.bull.javamelody:javamelody-core (3 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.47.0.

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in HtmlSessionInformationsReport.java in JavaMelody 1.46 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted X-Forwarded-For header.

AnalysisAI

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in HtmlSessionInformationsReport.java in JavaMelody 1.46 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted X-Forwarded-For header. Affected products include: Emeric Vernat Javamelody.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.