dbcve.org
Adaptive Server EnterpriseApplication · Sap

CVE-2022-31595

HIGH · 8.8 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
SAP Financial Consolidation - version 1010,�does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges.

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

SAP Financial Consolidation version 1010 contains a broken access control vulnerability where proper authorization checks are not enforced for authenticated users, allowing privilege escalation. An attacker with valid credentials can bypass intended security restrictions to access functionality or data beyond their authorized scope.

MitigationApply SAP security patches for this vulnerability when available. In the interim, implement compensating controls such as strict role-based access control validation at the application layer and monitor for unauthorized access patterns.

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
Adaptive Server EnterpriseApplication
Affected:= kernel_7.22= kernel_7.49= kernel_7.53= krnl64nuc_7.22= krnl64nuc_7.22ext= krnl64nuc_7.49= krnl64uc_7.22= krnl64uc_7.22ext= krnl64uc_7.49= krnl64uc_7.53

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify SAP Adaptive Server Enterprise installation
    Run 'sybase -V' or check for ASE binaries in /opt/sap or /sybase directories. Query the server with 'select @@version' or 'sp_version' to confirm the product and build version.
    Affected if The product is confirmed as SAP Adaptive Server Enterprise and the kernel version matches any of these: kernel_7.22, kernel_7.49, kernel_7.53, krnl64nuc_7.22, krnl64nuc_7.22ext, krnl64nuc_7.49, krnl64uc_7.22, krnl64uc_7.22ext, krnl64uc_7.49, or krnl64uc_7.53
  2. Verify the kernel version number
    Execute 'sp_version' or query 'select @@kernel_build' from a privileged login. Alternatively, check the $SYBASE/interfaces file or the installation logs for the specific kernel version string.
    Affected if The returned kernel version exactly matches one of the versions listed in the affected products (e.g., kernel_7.22, krnl64uc_7.53, etc.)
  3. Review role-based access control configuration
    Query system tables: select name, suid from sysxrole; select * from sysloginroles; Check for excessive role assignments with 'sp_displaylogin' for each user and verify no standard users have roles like 'sa_role', 'sso_role', or 'oper_role' that they should not possess.
    Affected if Standard authenticated users possess elevated roles (sa_role, sso_role) that grant access beyond their authorized scope, indicating the broken access control is exploitable.
  4. Audit permission grants on critical stored procedures
    Run 'sp_helprotect' on high-privilege procedures such as sp_role, sp_modifylogin, and sp_password. Check sysprotects table for any execute permissions granted to public or unknown accounts.
    Affected if Execute permissions on privileged administrative procedures are granted to public or non-administrative users, allowing privilege escalation.

You are affected if SAP Adaptive Server Enterprise is running with any of the listed kernel versions AND unauthorized users can access elevated functionality beyond their assigned role permissions.

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 SAP security patches for this vulnerability when available. In the interim, implement compensating controls such as strict role-based access control validation at the application layer and monitor for unauthorized access patterns.

Fix this in Adaptive Server Enterprise 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-2022-31595 — 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-2022-31595 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