dbcve.org
Api ConnectApplication · Ibm

CVE-2023-47722

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-09
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
IBM API Connect V10.0.5.3 and V10.0.6.0 stores user credentials in browser cache which can be read by a local user. IBM X-Force ID: 271912.

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

IBM API Connect versions 10.0.5.3 and 10.0.6.0 improperly store user credentials in the browser cache, allowing a local user with access to the same machine to retrieve these cached credentials from browser storage.

MitigationImplement HTTP security headers (Cache-Control: no-store, no-cache; Pragma: no-cache) on responses containing authentication data to prevent browser caching of credentials, and review the application to ensure sensitive credentials are not stored in browser-accessible locations.

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
Api ConnectApplication
Affected:= 10.0.5.3= 10.0.6.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 the installed IBM API Connect version
    Access the API Connect admin console or use the apic CLI tool with 'apic version' or check the product information in the management interface
    Affected if The version is exactly 10.0.5.3 or 10.0.6.0
  2. Examine browser developer tools for cached credentials
    Open the browser's developer console (F12), navigate to the Application/Storage tab, and inspect Local Storage, Session Storage, and Cookies for any stored username/password values after authenticating to API Connect
    Affected if User credentials or sensitive authentication tokens are visible in browser storage locations
  3. Capture and inspect HTTP response headers for authentication endpoints
    Log into API Connect, use the browser's network tab or a proxy tool to capture requests to authentication endpoints, and review the response headers for Cache-Control and Pragma headers
    Affected if Responses containing authentication data lack 'Cache-Control: no-store, no-cache' and 'Pragma: no-cache' headers, indicating credentials may be cached by the browser
  4. Check browser cache directories for API Connect authentication data
    On the machine where the browser is installed, examine the browser's cache folder (e.g., %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache for Chrome) for files containing API Connect URL patterns or credential data
    Affected if Cached files related to API Connect authentication endpoints exist and contain sensitive credential information

A user is affected if they are running IBM API Connect version 10.0.5.3 or 10.0.6.0 and can observe credentials or missing security headers in browser storage/cache after authentication.

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 HTTP security headers (Cache-Control: no-store, no-cache; Pragma: no-cache) on responses containing authentication data to prevent browser caching of credentials, and review the application to ensure sensitive credentials are not stored in browser-accessible locations.

Recommended fix Moderate confidence

IBM API Connect 10.0.5.4 or later, or 10.0.6.1 or later (or latest stable 10.0.x release)

  1. Upgrade IBM API Connect to a version newer than 10.0.5.3 and 10.0.6.0 that includes the security fix for CVE-2023-47722
  2. Verify the upgrade in a non-production environment before deploying to production
  3. After upgrade, clear browser cache on all affected systems to remove any cached credentials
  4. Confirm the fix by checking that credentials are no longer stored in browser cache
Caveat Review IBM API Connect release notes for any breaking changes between affected and fixed versions before upgrading

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

Fix this in Api Connect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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