CVE-2017-16682
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 · uneditedSAP NetWeaver Internet Transaction Server (ITS), SAP Basis from 7.00 to 7.02, 7.30, 7.31, 7.40, from 7.50 to 7.52, allows an attacker with administrator credentials to inject code that can be executed by the application and thereby control the behavior of the application.
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 confidenceCVE-2017-16682 is a code injection vulnerability in SAP NetWeaver Internet Transaction Server (ITS) affecting SAP Basis versions 7.00-7.02, 7.30, 7.31, 7.40, and 7.50-7.52. An attacker with valid administrator credentials can inject malicious code that gets executed by the application, allowing full control over application behavior.
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 versions>= 7.00, <= 7.02>= 7.50, <= 7.52= 7.30= 7.31= 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Verify if Internet Transaction Server (ITS) is enabledCheck the SAP system profile parameters for ITS-related settings (e.g., icm/its-enable or similar ITS-related profile parameters) or access SAP transaction code SICF to verify if ITS services are activeAffected if ITS is enabled and running on the SAP system
-
Determine the installed SAP Basis versionAccess the SAP system and use transaction code SM37 or execute the SAP kernel version check command to identify the installed SAP Basis release and version numberAffected if The SAP Basis version falls within 7.00-7.02, 7.30, 7.31, 7.40, or 7.50-7.52
-
Identify ITS-related scripts and function modulesUse SAP transaction code SE37 (Function Builder) to review ITS-related function modules, and access the ITS script directory (typically under /sap/bc/its or similar paths in the SAP file system) to inspect active scriptsAffected if Unrecognized or malicious code is present in ITS scripts or function modules that was not authored by your organization
-
Review administrator access and recent administrator actionsUse SAP transaction code SM37 or SLG1 to review job logs and audit logs for recent administrator activity, and check transaction code SU01 for administrator account modificationsAffected if Unauthorized administrator accounts exist or suspicious administrator actions have been recorded
A user is affected if the SAP Internet Transaction Server (ITS) is enabled and the SAP Basis version falls within the affected range, or if malicious code is found in ITS scripts despite the version.
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 patches for this vulnerability. Additionally, restrict administrator access to only necessary personnel, review ITS scripts and function modules for malicious code, and implement strict input validation on all user-supplied data within the ITS.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16682 — 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-16682 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