dbcve.org
Dynamic TierApplication · Sap

CVE-2019-0381

MEDIUM · 5.5 CVSS v3.1 Published 2019-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
A binary planting in SAP SQL Anywhere, before version 17.0, SAP IQ, before version 16.1, and SAP Dynamic Tier, before versions 1.0 and 2.0, can result in the inadvertent access of files located in directories outside of the paths specified by the user.

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 confidence

A binary planting vulnerability in SAP SQL Anywhere (before 17.0), SAP IQ (before 16.1), and SAP Dynamic Tier (before 1.0/2.0) allows inadvertent access to files located in directories outside user-specified paths. This path traversal issue could allow an attacker to manipulate file access through maliciously placed binaries.

MitigationUpgrade SAP SQL Anywhere to version 17.0 or later, SAP IQ to version 16.1 or later, and SAP Dynamic Tier to versions 1.0/2.0 or later as specified in the SAP security notes.

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
Dynamic TierApplication
Affected:= 1.0= 2.0
Sap IqApplication
Affected:= 16.1
Sql AnywhereApplication
Affected:= 17.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Identify installed SAP product
    Check for SAP SQL Anywhere, SAP IQ, or SAP Dynamic Tier installation by looking for their respective binaries or services (dbsrv17, dbspawn, sa_config.sh for SQL Anywhere; IQ server processes for SAP IQ; Dynamic Tier components)
    Affected if Any of these three SAP products are installed on the system
  2. Determine SQL Anywhere version
    Run 'dbsrv17 -v' or look for version information in the installation directory (typically under /opt/sqlanywhere or similar). Check the dbeng* or dbsrv* binary version.
    Affected if Installed version is earlier than 17.0 (versions 16.x and below)
  3. Determine SAP IQ version
    Run 'iqsrv -v' or check the IQ server version via its startup logs or the installation directory. Look for binary version strings containing 'IQ' or 'Sybase IQ'.
    Affected if Installed version is earlier than 16.1 (version 16.0 and below)
  4. Determine SAP Dynamic Tier version
    Check the Dynamic Tier component version via its installation directory, startup scripts, or by querying the component directly with version flags. Look for directories containing 'dtil' or 'dynamic tier' in the SAP installation path.
    Affected if Installed version is 1.0 or 2.0 (these specific versions are affected)
  5. Check for vulnerable binary loading configuration
    Review the application PATH environment variable and any configuration files that specify directories for loading executable binaries. Look for world-writable directories in the PATH that could allow binary planting.
    Affected if World-writable or untrusted directories exist in the PATH before the SAP product binaries, allowing an attacker to place malicious substitute binaries

User is affected if they have SQL Anywhere version below 17.0, SAP IQ version below 16.1, or SAP Dynamic Tier versions 1.0 or 2.0, AND the PATH contains writable directories that could be exploited for binary planting.

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

Upgrade SAP SQL Anywhere to version 17.0 or later, SAP IQ to version 16.1 or later, and SAP Dynamic Tier to versions 1.0/2.0 or later as specified in the SAP security notes.

Fix this in Dynamic Tier Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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