dbcve.org
Environment Health And SafetyApplication · Sap

CVE-2014-8664

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 Product Safety (EHS-SAF) component in SAP Environment, Health, and Safety Management 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 the Product Safety (EHS-SAF) module of SAP Environment, Health, and Safety Management allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant risk of data exposure or manipulation.

MitigationApply the relevant SAP Security Note to address the SQL injection in EHS-SAF; additionally, implement input validation, use parameterized queries, and ensure the database user has least privilege to limit impact of any successful injection.

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
Environment Health And SafetyApplication
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. Verify EHS-SAF module installation
    Use SAP transaction code SE81 (Environment, Health & Safety) or check via SAP Solution Manager to determine if the EHS-SAF Product Safety module is installed in the system. You can also check via SAP System Landscape Directory or using transaction SE11 to search for EHS-related tables.
    Affected if The EHS-SAF module is installed and visible in the SAP system
  2. Identify active EHS-SAF transactions
    Check for active EHS-SAF related transaction codes such as EHS001 (Product Safety - Main Menu), EHS002 (Substance), EHS003 (Formula), or custom transactions in the EHS namespace. Use transaction SUIM (User Information System) to search for users with access to EHS transaction codes.
    Affected if Users have access to EHS-SAF transaction codes
  3. Check EHS-SAF web service exposure
    Review SAP Gateway (ICF) services and check if EHS-related web services are activated. Use transaction SICF to find active services under /sap/bc/rest/ or /sap/bc/esh/ paths related to EHS. Also check transaction SOAMANAGER for EHS-SAF exposed web service endpoints.
    Affected if EHS-SAF functionality is exposed via HTTP/HTTPS web services or RFC interfaces
  4. Examine database access permissions
    Review the database user credentials used by the EHS-SAF module. Use transaction DB02 or DBACOCKPIT to check the privileges assigned to the SAP schema user accessing the database for EHS tables (typically stored in tables with EHS* or SAF* prefixes).
    Affected if The database user has elevated privileges beyond minimal required access for EHS operations
  5. Review system logs for SQL injection indicators
    Use transaction SM37 or ST03N to examine job logs, and transaction SM19 for security audit logs. Look for unusual SQL patterns or failed authentication attempts targeting EHS-SAF transaction codes or tables. Check transaction SLG1 for application logs related to EHS.
    Affected if Suspicious SQL patterns or unauthorized database queries appear in logs related to EHS-SAF components

If the EHS-SAF module is installed and exposed via transactions, web services, or RFC interfaces in the SAP system, the environment is potentially affected by this SQL injection vulnerability.

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

Apply the relevant SAP Security Note to address the SQL injection in EHS-SAF; additionally, implement input validation, use parameterized queries, and ensure the database user has least privilege to limit impact of any successful injection.

Fix this in Environment Health And Safety Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8664 — 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-8664 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