CVE-2024-22318 json
IBM i Access Client Solutions information disclosure
published 2y ago modified 4mo ago also EUVD-2024-19879
- cvss
- 5.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 1
- Exploit-DB
Summary
IBM i Access Client Solutions (ACS) 1.1.2 through 1.1.4 and 1.1.4.3 through 1.1.9.4 is vulnerable to NT LAN Manager (NTLM) hash disclosure by an attacker modifying UNC capable paths within ACS configuration files to point to a hostile server. If NTLM is enabled, the Windows operating system will try to authenticate using the current user's session. The hostile server could capture the NTLM hash information to obtain the user's credentials. IBM X-Force ID: 279091.
Is CVE-2024-22318 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-51817)
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- EDB-51817 IBM i Access Client Solutions v1.1.2 - 1.1.4_ v1.1.4.3 - 1.1.9.4 - Remote Credential Theft remote, 2024-02-26
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- IBM i Access Client Solutions
Classification
References
-
ibm.com
/support/pages/node/7116091
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/279091
vdb-entry
-
packetstormsecurity.com
/files/177069/IBM-i-Access-Client-Solutions-Remote-Credential-Theft.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2024/Feb/7
mailing-list, third-party-advisory
Sources
- CVE List CVE-2024-22318
- NVD CVE-2024-22318
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.