CVE-2022-27670
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 SQL Anywhere - version 17.0, allows an authenticated attacker to prevent legitimate users from accessing a SQL Anywhere database server by crashing the server with some queries that use indirect identifiers.
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 confidenceSAP SQL Anywhere version 17.0 contains a denial-of-service vulnerability where an authenticated attacker can crash the database server by executing certain queries that use indirect identifiers, preventing legitimate users from accessing the database.
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= 17.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 installed SAP SQL Anywhere versionUse the dbeng17 or dbsrv17 version command, or check the product information via the SQL Anywhere console or installed programs listAffected if The installed version is exactly 17.0.0
-
Determine if authenticated user accounts existQuery the system catalog for user accounts (e.g., SELECT * FROM SYS.SYSUSER) or review defined database users in the SQL Anywhere security settingsAffected if There are authenticated users with database access privileges
-
Check if non-administrative users have query execution privilegesReview user permissions using the GRANT statement outputs or query system views that show privileges assigned to each user (e.g., SYS.SYSPERMISSION)Affected if Non-administrative users have permissions to execute SELECT or other query statements
-
Verify the database server is running and accepting connectionsCheck for active dbeng17 or dbsrv17 processes on the host, or attempt a connection to the databaseAffected if The server is running and accessible, making the DoS impact possible
You are affected if SAP SQL Anywhere version 17.0 is running and there are authenticated users (especially non-administrative ones) with query execution privileges that could trigger the indirect identifier vulnerability.
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.
dbcve · scopedApply the latest SAP security patch for SQL Anywhere 17.0. As a temporary measure, restrict query execution privileges for non-administrative authenticated users until the patch can be deployed.
SAP SQL Anywhere 17.0.10 or later (or the latest available 17.0.x patch from SAP)
- 1. Log in to the SAP Support Portal at launchpad.support.sap.com
- 2. Search for CVE-2022-27670 or SAP Note related to SQL Anywhere 17.0 security vulnerability
- 3. Download and apply the appropriate hotfix or patch for SAP SQL Anywhere version 17.0
- 4. After applying the patch, restart the SQL Anywhere database server
- 5. Verify that the server runs without crashes when executing queries with indirect identifiers
- 6. Test normal database operations to confirm the fix does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27670 — 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-2022-27670 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