[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fWjJf0Vy29dnfqTeDR3XzgVlvv45-BG7LgbhLAyUd4Cs":3,"g5a-risk:CVE-2024-22318":144},{"success":4,"data":5,"meta":141},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":40,"epssPercentile":28,"epssTimeSeries":41,"severity":42,"affectedProducts":43,"affectedProductsCount":49,"references":50,"referencesCount":79,"weaknesses":80,"weaknessesCount":97,"isActivelyExploited":98,"cisaInfo":28,"otxData":28,"relatedBlogPosts":99,"seoMetadata":100,"configurations":125,"relatedVendorCves":139,"notableEvents":140},"CVE-2024-22318","What is CVE-2024-22318?","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.","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 mod...","2024-02-09T01:15:09.44","2026-06-17T07:11:10.573",5.5,"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":37,"CVSSMetricV2":38,"CVSSMetricV40":39},[16,31],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":29,"ImpactScore":30},"psirt@us.ibm.com","Secondary",{"Version":20,"VectorString":21,"AttackVector":22,"AttackComplexity":23,"PrivilegesRequired":24,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":23,"IntegrityImpact":24,"AvailabilityImpact":24,"BaseScore":26,"BaseSeverity":27,"ExploitCodeMaturity":28,"RemediationLevel":28,"ReportConfidence":28,"TemporalScore":28,"TemporalSeverity":28,"ConfidentialityRequirement":28,"IntegrityRequirement":28,"AvailabilityRequirement":28,"ModifiedAttackVector":28,"ModifiedAttackComplexity":28,"ModifiedPrivilegesRequired":28,"ModifiedUserInteraction":28,"ModifiedScope":28,"ModifiedConfidentialityImpact":28,"ModifiedIntegrityImpact":28,"ModifiedAvailabilityImpact":28,"EnvironmentalScore":28,"EnvironmentalSeverity":28},"3.1","CVSS:3.1\u002FAV:L\u002FAC:H\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N","LOCAL","HIGH","NONE","UNCHANGED",5.1,"MEDIUM",null,1.4,3.6,{"Source":32,"Type":33,"CVSSData":34,"ExploitabilityScore":36,"ImpactScore":30},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":22,"AttackComplexity":35,"PrivilegesRequired":35,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":23,"IntegrityImpact":24,"AvailabilityImpact":24,"BaseScore":12,"BaseSeverity":27,"ExploitCodeMaturity":28,"RemediationLevel":28,"ReportConfidence":28,"TemporalScore":28,"TemporalSeverity":28,"ConfidentialityRequirement":28,"IntegrityRequirement":28,"AvailabilityRequirement":28,"ModifiedAttackVector":28,"ModifiedAttackComplexity":28,"ModifiedPrivilegesRequired":28,"ModifiedUserInteraction":28,"ModifiedScope":28,"ModifiedConfidentialityImpact":28,"ModifiedIntegrityImpact":28,"ModifiedAvailabilityImpact":28,"EnvironmentalScore":28,"EnvironmentalSeverity":28},"LOW",1.8,[],[],[],0.00573,[40,40,40,40,40,40,40],"Medium",[44],{"vendor":45,"product":46,"version":47,"criteria":48,"vulnerable":4},"ibm","i_access_client_solutions","*","cpe:2.3:a:ibm:i_access_client_solutions:*:*:*:*:*:*:*:*",1,[51,57,62,66,71,73,75,77],{"url":52,"source":53,"tags":54},"http:\u002F\u002Fpacketstormsecurity.com\u002Ffiles\u002F177069\u002FIBM-i-Access-Client-Solutions-Remote-Credential-Theft.html","Packetstormsecurity",[55,56],"Third Party Advisory","VDB Entry",{"url":58,"source":59,"tags":60},"http:\u002F\u002Fseclists.org\u002Ffulldisclosure\u002F2024\u002FFeb\u002F7","Seclists",[61,55],"Mailing List",{"url":63,"source":64,"tags":65},"https:\u002F\u002Fexchange.xforce.ibmcloud.com\u002Fvulnerabilities\u002F279091","Ibmcloud",[56],{"url":67,"source":68,"tags":69},"https:\u002F\u002Fwww.ibm.com\u002Fsupport\u002Fpages\u002Fnode\u002F7116091","Ibm",[70],"Vendor Advisory",{"url":52,"source":53,"tags":72},[55,56],{"url":58,"source":59,"tags":74},[61,55],{"url":63,"source":64,"tags":76},[56],{"url":67,"source":68,"tags":78},[70],8,[81,89],{"id":82,"name":83,"description":84,"extendedDescription":85,"status":86,"abstraction":87,"structure":88},"CWE-327","Use of a Broken or Risky Cryptographic Algorithm","The product uses a broken or risky cryptographic algorithm or protocol.","Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts.\nIt is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known-insecure algorithm is dangerous because a determined adversary may be able to break the algorithm and compromise whatever data has been protected.\nSince the state of cryptography advances so rapidly, it is common for an algorithm to be considered \"unsafe\" even if it was once thought to be strong. This can happen when new attacks are discovered, or if computing power increases so much that the cryptographic algorithm no longer provides the amount of protection that was originally thought.\nFor a number of reasons, this weakness is even more challenging to manage with hardware deployment of cryptographic algorithms as opposed to software implementation. First, if a flaw is discovered with hardware-implemented cryptography, the flaw cannot be fixed in most cases without a recall of the product, because hardware is not easily replaceable like software. Second, because the hardware product is expected to work for years, the adversary's computing power will only increase over time.","Draft","Class","Simple",{"id":90,"name":91,"description":92,"extendedDescription":93,"status":94,"abstraction":95,"structure":96},"CWE-384","Session Fixation","Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.","Such a scenario is commonly observed when:\nIn the generic exploit of session fixation vulnerabilities, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to associate, and possibly authenticate, against the server using that session identifier, giving the attacker access to the user's account through the active session.","Incomplete","Compound","Composite",2,false,[],{"title":101,"metaDescription":102,"keywords":103,"canonicalUrl":104,"structuredData":105},"What is CVE-2024-22318? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2024-22318, a medium severity cyber security vulnerability from 2024. IBM i Access Client Solutions (ACS) 1.1.2 through 1.1.4 a...","CVE-2024-22318, CVE-2024-22318 vulnerability, CVE-2024-22318 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2024, CVSS score, exploit, patch, remediation, ibm security, i_access_client_solutions vulnerability","\u002Fwhat-is\u002Fcve-2024-22318",{"@context":106,"@type":107,"headline":101,"description":102,"datePublished":10,"dateModified":11,"author":108,"publisher":112,"about":116,"mainEntityOfPage":120,"articleSection":123,"keywords":124},"https:\u002F\u002Fschema.org","TechArticle",{"@type":109,"name":110,"url":111},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":109,"name":110,"url":111,"logo":113},{"@type":114,"url":115},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":117,"name":6,"description":118,"additionalType":119},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":121,"@id":122},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2024-22318","Cybersecurity","CVE-2024-22318, CVE-2024-22318 vulnerability, CVE-2024-22318 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[126],{"Operator":28,"Negate":28,"Nodes":127},[128],{"Operator":129,"Negate":98,"CPEMatch":130},"OR",[131,135],{"Vulnerable":4,"Criteria":48,"MatchCriteriaID":132,"VersionStartExcluding":28,"VersionStartIncluding":133,"VersionEndExcluding":28,"VersionEndIncluding":134},"531AF116-53A2-47C9-944E-C7E2CA2ADF9B","1.1.2","1.1.4",{"Vulnerable":4,"Criteria":48,"MatchCriteriaID":136,"VersionStartExcluding":28,"VersionStartIncluding":137,"VersionEndExcluding":28,"VersionEndIncluding":138},"BBE9A4FD-776F-4981-A57F-9E69849577E4","1.1.4.3","1.1.9.4",[],[],{"lastModified":11,"cacheTime":142,"version":143},1792284593611,"2.0",{"score":145,"band":146,"action":147,"scoredAt":148},20,"Low","Monitor","2026-10-16T07:00:43.767517+00:00"]