CVE-2013-6814
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe J2EE Engine in SAP NetWeaver 6.40, 7.02, and earlier allows remote attackers to redirect users to arbitrary web sites, conduct phishing attacks, and obtain sensitive information (cookies and SAPPASSPORT) via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe J2EE Engine in SAP NetWeaver 6.40, 7.02, and earlier contains an open redirect vulnerability allowing remote attackers to hijack sessions via unspecified vectors that can steal cookies and SAPPASSPORT authentication tokens, enabling phishing and session hijacking attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.02= 6.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver installation and versionAccess the SAP Management Console (SAP MC) or use transaction SM51 to list installed SAP system instances and their release versions. Alternatively, check the SAP kernel version via the 'kernel' directory or transaction SXMB_MONI for system release information.Affected if The installed SAP NetWeaver version is 6.40 or 7.02, or any version earlier than 7.02.
-
Confirm J2EE Engine component is runningIn the SAP Management Console, expand the instance tree and verify that the J2EE Engine (often labeled as 'J2EE Server' or 'Java Engine') process is active. You can also use transaction J2EE_G to access the J2EE Engine administration console.Affected if The J2EE Engine is running and accessible via network services.
-
Verify NetWeaver version against affected rangesCross-reference the discovered NetWeaver release version from step 1 against the affected ranges: version 6.40 (any patch) or version 7.02 and below. Obtain the exact release via transaction SM37 or by checking the SAP System Information in the SAP Logon pad properties.Affected if The NetWeaver release is confirmed as 6.40 or 7.02 or any version numbered lower than 7.02.
-
Check J2EE web dispatcher or ICM exposureInspect the SAP Internet Communication Manager (ICM) configuration via transaction SMICM or the web dispatcher configuration to identify publicly accessible J2EE endpoints. Look for URL patterns in the ICM log that may indicate redirect behavior.Affected if The J2EE Engine web interfaces are exposed externally or accessible without strong authentication controls, allowing redirect vectors.
You are affected if your SAP NetWeaver installation is version 6.40 or 7.02 (or earlier) and the J2EE Engine component is active and accessible, as this configuration matches the vulnerable version range for CVE-2013-6814.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply relevant SAP security notes to patch the J2EE Engine vulnerability; consider upgrading to a supported NetWeaver version if still on 6.40 or early 7.02.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data