Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2013-1592: Buffer Overflow in SAP NetWeaver Message Server _MsJ2EE_AddStatistics()

Published Jan 23, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS24.4%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
SAP SE
IdentifiersCVE-2013-1592CWE-120 · Buffer Copy without Checking Size…

A buffer overflow vulnerability exists in the _MsJ2EE_AddStatistics() function of the SAP NetWeaver Message Server. The vulnerability is triggered when specially crafted packets are sent to the remote TCP ports 36NN or 39NN, affecting SAP NetWeaver versions 2004s, 7.01 SR1, 7.02 SP06, and 7.30 SP04. This flaw allows a remote attacker to overflow a buffer and potentially execute arbitrary code on the affected system.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution with the privileges of the SAP Message Server process, potentially leading to full system compromise and lateral movement within the SAP landscape.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the affected TCP ports (36NN and 39NN) to trusted hosts only. Monitor network traffic for suspicious or malformed packets targeting the Message Server. Consider deploying intrusion detection systems to alert on exploitation attempts.

Remediation

Patch, then assume compromise.

Apply the official SAP security patches for the affected NetWeaver versions as soon as possible. Refer to SAP Security Notes for CVE-2013-1592 for detailed patching instructions.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SAP SENetWeaverapplication
FAQ

Frequently asked questions

Is CVE-2013-1592 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-1592 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-1592?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2013-1592.
Is there a patch for CVE-2013-1592?
Apply the official SAP security patches for the affected NetWeaver versions as soon as possible. Refer to SAP Security Notes for CVE-2013-1592 for detailed patching instructions.
What products are affected by CVE-2013-1592?
SAP SE NetWeaver.
How severe is CVE-2013-1592?
CVE-2013-1592 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 24.4% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.