I Access Client SolutionsApplication · Ibm

CVE-2023-45184

HIGH · 7.5 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 1.1.9.4 or later.
See remediation →
84/100
Remediation priority · High
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
IBM i Access Client Solutions 1.1.2 through 1.1.4 and 1.1.4.3 through 1.1.9.3 could allow an attacker to obtain a decryption key due to improper authority checks. IBM X-Force ID: 268270.

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

IBM i Access Client Solutions versions 1.1.2-1.1.4 and 1.1.4.3-1.1.9.3 contain improper authority checks that allow an attacker to obtain a decryption key, enabling unauthorized access to encrypted data.

MitigationUpgrade to a patched version of IBM i Access Client Solutions. If immediate upgrade is not possible, restrict access to the application and monitor for unauthorized access attempts.

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
I Access Client SolutionsApplication
Affected:>= 1.1.2, <= 1.1.4>= 1.1.4.3, < 1.1.9.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 IBM i Access Client Solutions version
    Open the application and navigate to Help > About, or check the version displayed on the login screen. Alternatively, check the installation package or documentation that came with the software.
    Affected if The version displayed cannot be determined or is not visible.
  2. Compare installed version against CVE ranges
    Note the full version number (for example, 1.1.5, 1.1.9, or 1.1.9.4) and compare it to the affected ranges: 1.1.2 through 1.1.4, or 1.1.4.3 through 1.1.9.3.
    Affected if The installed version falls within 1.1.2-1.1.4 or 1.1.4.3-1.1.9.3.
  3. Confirm version is not the patched release
    Verify the exact version number. Versions 1.1.9.4 and later contain the fix. If your version shows 1.1.9.3 or lower (or 1.1.4.x where x is less than 3), the vulnerability is present.
    Affected if The installed version is 1.1.9.3 or lower, or falls in the 1.1.2-1.1.4 range.
  4. Check for use of encrypted data features
    Determine if the environment uses IBM i Access Client Solutions to access encrypted data or sensitive information stored on IBM i systems. Review any configured data encryption or secure credential storage features.
    Affected if Encrypted data or sensitive credentials are accessed through the vulnerable application version.

A user is affected if IBM i Access Client Solutions version 1.1.2-1.1.4 or 1.1.4.3-1.1.9.3 is installed and the application is used to access encrypted data.

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 1.1.9.4 or later
Fixed in 1.1.9.4
Interim mitigation

Upgrade to a patched version of IBM i Access Client Solutions. If immediate upgrade is not possible, restrict access to the application and monitor for unauthorized access attempts.

Recommended fix High confidence

IBM i Access Client Solutions 1.1.9.4 or later

  1. 1. Download the latest version of IBM i Access Client Solutions (version 1.1.9.4 or later) from the official IBM website or your authorized IBM distribution channel
  2. 2. Ensure all active sessions of IBM i Access Client Solutions are closed before upgrading
  3. 3. Run the IBM i Access Client Solutions installer with appropriate administrative privileges
  4. 4. Follow the on-screen installation prompts to complete the upgrade
  5. 5. After installation, verify the new version by checking Help > About in the application
  6. 6. Test critical functionality to ensure the upgrade did not disrupt existing workflows
Caveat Standard upgrade precautions apply - test in a non-production environment first; review IBM release notes for any functional changes between your current version and 1.1.9.4

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

Fix this in I Access Client Solutions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45184 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