CVE-2017-7717
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 · uneditedSQL injection vulnerability in the getUserUddiElements method in the ES UDDI component in SAP NetWeaver AS Java 7.4 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, aka SAP Security Note 2356504.
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 · high confidenceSQL injection vulnerability in the getUserUddiElements method in the ES UDDI component of SAP NetWeaver AS Java 7.4 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
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.40CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 AS Java versionAccess SAP NetWeaver Administrator (NWA) via http://<host>:5<instance>00/nwa or use SAP MMC to check the AS Java version in the system informationAffected if The installed version is 7.40 (exactly) - note that versions 7.40 through 7.54 may contain this component; only 7.40 is explicitly listed as affected in this CVE
-
Verify ES UDDI component is enabledIn SAP NetWeaver Administrator, navigate to Configuration > Infrastructure > Application Modules or check the SAP System Landscape Directory (SLD) for the ES UDDI Enterprise Service repository registrationAffected if The UDDI Enterprise Service component is present and running on the system
-
Confirm getUserUddiElements method is accessibleCheck SAP NetWeaver Administrator under SOA > Enterprise Services > UDDI or review the UDDI service WSDL endpoint for the getUserUddiElements operationAffected if The getUserUddiElements method is exposed via the UDDI service endpoint and accessible to authenticated users
-
Review application logs for SQL injection indicatorsAccess SAP NetWeaver Developer Traces via NWA > Troubleshooting > Logs and Traces > Developer Traces, or check the default trace file defaultTrace*.trc in the work directory for SQL syntax patterns or errors around UDDI callsAffected if Unusual SQL syntax, error messages containing SELECT/INSERT/UPDATE statements, or database errors appear in logs following UDDI user element queries
A user is affected if they run SAP NetWeaver AS Java 7.40 with the ES UDDI component enabled and the getUserUddiElements method is exposed to authenticated users without the 2356504 patch applied.
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 SAP Security Note 2356504 to patch the vulnerable getUserUddiElements method with parameterized queries; until the patch is applied, restrict network access to the UDDI service and monitor for suspicious SQL patterns in application logs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7717 — 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-2017-7717 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