dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2023-49112

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Kiuwan provides an API endpoint /saas/rest/v1/info/application to get information about any application, providing only its name via the "application" parameter. This endpoint lacks proper access control mechanisms, allowing other authenticated users to read information about applications, even though they have not been granted the necessary rights to do so. This issue affects Kiuwan SAST: <master.1808.p685.q13371

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

The /saas/rest/v1/info/application endpoint accepts an application name parameter but fails to verify the authenticated user has authorization to access that specific application. This is a classic Insecure Direct Object Reference (IDOR) vulnerability where any authenticated user can retrieve sensitive information about applications they do not own or have been granted access to.

MitigationImplement proper authorization checks to verify the currently authenticated user has explicit permissions to view the requested application before returning any data. This requires validating user-application access rights at the service layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Availability
None

CVSS:3.1/AV:N/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. Verify the vulnerable endpoint exists
    Check your application's routing configuration or API documentation for the presence of the /saas/rest/v1/info/application endpoint. This is typically defined in your REST API router or route definitions.
    Affected if The endpoint is exposed and accessible in your environment
  2. Confirm authentication is required
    Attempt to access the /saas/rest/v1/info/application endpoint without providing credentials. Verify that the endpoint requires authentication (returns 401 or similar for unauthenticated requests).
    Affected if The endpoint accepts unauthenticated requests, making it more severe, but the CVE specifically requires authentication to exploit
  3. Test cross-application data access
    Log in as a user who has access to Application A only. Send a request to /saas/rest/v1/info/application?name=ApplicationB (where ApplicationB is an application the user does not own or have access to). Inspect the response for sensitive information about ApplicationB.
    Affected if The endpoint returns sensitive information about applications the authenticated user has not been granted access to, indicating the IDOR vulnerability is present
  4. Review application permission configuration
    Examine your application's user-to-application mapping or access control list configuration. Confirm how user-application permissions are defined and stored.
    Affected if The permission system exists but is not being validated by the /saas/rest/v1/info/application endpoint

A user is affected if they can access sensitive information about applications they do not own or have not been granted access to by making requests to the /saas/rest/v1/info/application endpoint with application names outside their authorized scope.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks to verify the currently authenticated user has explicit permissions to view the requested application before returning any data. This requires validating user-application access rights at the service layer.

Recommended fix Moderate confidence

master.1808.p685.q13371 or later

  1. Contact Kiuwan vendor support to obtain the security patch for CVE-2023-49112
  2. Request the patched version (master.1808.p685.q13371 or later) that addresses the authorization bypass in /saas/rest/v1/info/application
  3. Apply the vendor-provided patch following their installation instructions
  4. Verify the patch was applied successfully by checking the Kiuwan version
  5. Test that the /saas/rest/v1/info/application endpoint now properly enforces access controls - authenticated users should only see applications they have been explicitly granted access to
  6. Confirm that users without application access receive appropriate authorization errors when attempting to access unauthorized application information

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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