CVE-2016-7402
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 ASE 16.0 SP02 PL03 and prior versions allow attackers who own SourceDB and TargetDB databases to elevate privileges to sa (system administrator) via dbcc import_sproc SQL injection.
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 dbcc import_sproc stored procedure of SAP Adaptive Server Enterprise (ASE) versions 16.0 SP02 PL03 and prior allows authenticated users who own SourceDB and TargetDB databases to execute arbitrary SQL code and escalate privileges to the sa (system administrator) role, granting full system-level access.
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<= 16.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 ASE versionRun 'select @@version' or 'sp_version' in isql to retrieve the installed version numberAffected if The version is 16.0 or lower, including any SP02 PL03 or earlier service pack level
-
Verify if SourceDB database existsRun 'sp_helpdb SourceDB' to check whether the SourceDB database exists in the environmentAffected if SourceDB database is present in the system
-
Verify if TargetDB database existsRun 'sp_helpdb TargetDB' to check whether the TargetDB database exists in the environmentAffected if TargetDB database is present in the system
-
Check ownership of SourceDBRun 'sp_helpdb SourceDB' and examine the owner field to determine if a regular user (non-sa) owns the databaseAffected if A non-privileged user account owns SourceDB
-
Check ownership of TargetDBRun 'sp_helpdb TargetDB' and examine the owner field to determine if a regular user (non-sa) owns the databaseAffected if A non-privileged user account owns TargetDB
-
Determine current user privilegesRun 'select suser_name()' to identify the current logged-in user, then run 'sp_helpuser' to list user roles and permissionsAffected if The current user is NOT a member of the sa_role but owns both SourceDB and TargetDB databases
A user is affected if they are running SAP ASE version 16.0 or lower AND they own both the SourceDB and TargetDB databases, allowing them to execute the vulnerable dbcc import_sproc stored procedure and escalate privileges.
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 dataUpgrade SAP ASE to a version beyond 16.0 SP02 PL03, or apply the relevant security patch from SAP. Additionally, restrict database ownership and enforce least-privilege principles to limit which users can own SourceDB and TargetDB.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7402 — 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-2016-7402 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