dbcve.org
Contract AccountingApplication · Sap

CVE-2014-8668

HIGH · 7.5 CVSS v2.0 Published 2014-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection vulnerability in SAP Contract Accounting allows remote attackers to execute arbitrary SQL commands 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 confidence

SQL injection vulnerability in SAP Contract Accounting enables remote attackers to execute arbitrary SQL commands through unsanitized input vectors in the application layer, potentially allowing complete database compromise.

MitigationImplement parameterized queries or prepared statements with proper input validation and sanitization across all user-supplied fields in the Contract Accounting module; apply SAP security notes if available.

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
Contract AccountingApplication
Affected:all versions

CVSS 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
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAP Contract Accounting installation
    Access SAP GUI and run transaction code SE11 or SPAM to list installed software components. Look for module 'Contract Accounting' (often labeled as 'FI-CA' or 'Contract Accounting' in SAP system landscape) in the installed components.
    Affected if SAP Contract Accounting module is present and active in the SAP system
  2. Identify active Contract Accounting transactions
    Use transaction code SE93 or search in SAP Menu for transactions associated with Contract Accounting (commonly FI-CA related transactions such as FCI2, FPCO, or custom transactions in the /SAP*/FI-CA namespace). Document which Contract Accounting transactions are available to users.
    Affected if Contract Accounting transactions are accessible in the SAP system
  3. Check for custom ABAP enhancements
    Use transaction code SE80 or SE24 to examine any custom ABAP code, user exits, or Business Add-Ins (BAdIs) implemented in the Contract Accounting module. Look for direct SQL statements (SELECT, UPDATE, INSERT, DELETE) that process user input without using SAP standard APIs or parameterized queries.
    Affected if Custom ABAP code exists in Contract Accounting that handles user input with direct SQL constructs
  4. Review web service endpoints for Contract Accounting
    Use transaction code SOAMANAGER or SICF to examine web service definitions exposed for Contract Accounting. Check if any Contract Accounting related web services accept input parameters that could be passed to database queries.
    Affected if Contract Accounting web services are exposed and accept user-supplied parameters without proper validation
  5. Audit RFC and interface configurations
    Use transaction code SM59 to review RFC destinations and interface configurations related to Contract Accounting. Examine if external interfaces pass data to SQL queries without input validation.
    Affected if RFC interfaces or external interfaces for Contract Accounting handle input data without parameterized query usage

A defender is affected if SAP Contract Accounting is installed and any custom code, web services, or interfaces handle user input in direct SQL statements without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements with proper input validation and sanitization across all user-supplied fields in the Contract Accounting module; apply SAP security notes if available.

Fix this in Contract Accounting Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8668 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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