CVE-2014-1961
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 · uneditedUnspecified vulnerability in the Portal WebDynPro in SAP NetWeaver allows remote attackers to obtain sensitive path information via unknown attack 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 confidenceThis is an information disclosure vulnerability in SAP NetWeaver's Portal WebDynPro component. Remote attackers can obtain sensitive path information through unspecified attack vectors. The vulnerability allows discovery of internal file system paths which could aid in reconnaissance and further exploitation.
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 dataall versionsCVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 installationCheck for SAP NetWeaver processes running on the system (e.g., using task manager or 'ps' command on Unix), or look for SAP installation directories (commonly under /sapmnt/<SID> or C:\sapmnt\<SID> on Windows)Affected if SAP NetWeaver is installed and running on the system
-
Verify WebDynPro component is enabledCheck the SAP Portal configuration for WebDynPro applications. This can typically be done via SAP Management Console or by checking the SAP Web Dispatcher configuration for WebDynpro-related URL patterns (such as /webdynpro/)Affected if WebDynPro component is enabled and accessible via the SAP Portal
-
Confirm WebDynPro accessibilityTest if the WebDynPro endpoint is reachable by attempting to access a known WebDynPro URL pattern (such as http://<host>/sap/bc/webdynpro) or checking via SAP transaction code SICF to verify WebDynPro services are activeAffected if WebDynPro services are active and exposed via the web interface
-
Check for path disclosure exposureSince the attack vectors are unspecified, the most practical check is to compare your SAP NetWeaver version against vendor documentation or check if SAP security note 1981612 (or subsequent patches) has been applied. Without the patch, any WebDynPro request could potentially leak path informationAffected if WebDynPro is accessible and the relevant SAP security patch for CVE-2014-1961 has not been applied
If SAP NetWeaver with WebDynPro is running and the security patch for CVE-2014-1961 has not been applied, the environment is affected by this path information disclosure vulnerability.
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 the relevant SAP security patch for CVE-2014-1961. Ensure WebDynPro applications have proper authentication and authorization controls, and restrict access to the SAP Portal to trusted networks.
- Consultation8.0 h
- Implementation12.0 h
- Testing20.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1961 — 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-2014-1961 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