dbcve.org
Cloud Security Services Integration LibraryApplication · Sap

CVE-2023-50422

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 2.17.0 / 3.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
SAP BTP Security Services Integration Library ([Java] cloud-security-services-integration-library) - versions below 2.17.0 and versions from 3.0.0 to before 3.3.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.

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

The SAP BTP Security Services Integration Library (cloud-security-services-integration-library) versions below 2.17.0 and 3.0.0 to before 3.3.0 contain a privilege escalation vulnerability that allows an unauthenticated attacker to gain arbitrary permissions within the application under certain conditions.

MitigationUpgrade the cloud-security-services-integration-library to version 2.17.0 or 3.3.0 or later to remediate the vulnerability.

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
Cloud Security Services Integration LibraryApplication
Affected:< 2.17.0>= 3.0.0, < 3.3.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the library JAR or dependency file
    Find the cloud-security-services-integration-library JAR file in your application lib directory, or check your build configuration (Maven pom.xml, Gradle build.gradle, or npm package.json) for the declared version of the dependency.
    Affected if The declared or packaged version is below 2.17.0, or is 3.0.0 through 3.2.x inclusive.
  2. Query the runtime version
    If the library exposes a version endpoint or can be queried at runtime, invoke it to retrieve the actual running version number.
    Affected if The runtime version matches the affected ranges: < 2.17.0 or >= 3.0.0 and < 3.3.0.
  3. Inspect the application manifest
    Review the application's manifest file (such as MANIFEST.MF inside the JAR, or a dependency BOM file) for the embedded library version.
    Affected if The manifest shows a version that falls within the affected ranges.
  4. Verify the effective dependency version
    Run your build tool's dependency tree command (mvn dependency:tree, gradle dependencies, or npm ls) to resolve the actual resolved version of the library.
    Affected if The effective version is < 2.17.0 or >= 3.0.0 and < 3.3.0.

A user is affected if the installed or packaged version of cloud-security-services-integration-library is below 2.17.0, or is 3.0.0 through 3.2.x.

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.

dbcve · scoped
Upgrade available Upgrade to 2.17.0 / 3.3.0 or later
Fixed in 2.17.03.3.0
Interim mitigation

Upgrade the cloud-security-services-integration-library to version 2.17.0 or 3.3.0 or later to remediate the vulnerability.

Recommended fix High confidence

2.17.0 or 3.3.0 (depending on major version line)

  1. Identify the current version of cloud-security-services-integration-library in your project dependency configuration (pom.xml, build.gradle, or equivalent)
  2. Determine which major version line your project follows (2.x or 3.x)
  3. If using version 2.x: upgrade to version 2.17.0 or later
  4. If using version 3.x: upgrade to version 3.3.0 or later
  5. Update the dependency version in your build configuration file
  6. Rebuild and test the application to ensure compatibility
  7. Verify the new library version is correctly resolved in your dependency tree

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Security Services Integration Library Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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