[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_fib8rjkOVQo5_OXfZXNzSJLVSfZ6G1Z6y2SsHQNQbY":3,"g5a-risk:CVE-2024-22164":119},{"success":4,"data":5,"meta":116},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":36,"epssPercentile":26,"epssTimeSeries":37,"severity":38,"affectedProducts":39,"affectedProductsCount":45,"references":46,"referencesCount":59,"weaknesses":60,"weaknessesCount":76,"isActivelyExploited":77,"cisaInfo":26,"otxData":26,"relatedBlogPosts":78,"seoMetadata":79,"configurations":104,"relatedVendorCves":114,"notableEvents":115},"CVE-2024-22164","What is CVE-2024-22164?","In Splunk Enterprise Security (ES) versions below 7.1.2, an attacker can use investigation attachments to perform a denial of service (DoS) to the Investigation. The attachment endpoint does not properly limit the size of the request which lets an attacker cause the Investigation to become inaccessible.","In Splunk Enterprise Security (ES) versions below 7.1.2, an attacker can use investigation attachments to perform a denial of service (DoS) to the Investigat...","2024-01-09T17:15:12.323","2026-06-17T07:10:51.693",4.3,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:L",{"CVSSMetricV31":15,"CVSSMetricV30":33,"CVSSMetricV2":34,"CVSSMetricV40":35},[16,29],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"prodsec@splunk.com","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":22,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":26,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","NETWORK","LOW","NONE","UNCHANGED","MEDIUM",null,2.8,1.4,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":22,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":26,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},[],[],[],0.00457,[36,36,36,36,36,36,36],"Medium",[40],{"vendor":41,"product":42,"version":43,"criteria":44,"vulnerable":4},"splunk","enterprise_security","*","cpe:2.3:a:splunk:enterprise_security:*:*:*:*:*:*:*:*",1,[47,52,55,57],{"url":48,"source":49,"tags":50},"https:\u002F\u002Fadvisory.splunk.com\u002Fadvisories\u002FSVD-2024-0101","Splunk",[51],"Vendor Advisory",{"url":53,"source":49,"tags":54},"https:\u002F\u002Fresearch.splunk.com\u002Fapplication\u002Fbb85b25e-2d6b-4e39-bd27-50db42edcb8f\u002F",[51],{"url":48,"source":49,"tags":56},[51],{"url":53,"source":49,"tags":58},[51],4,[61,69],{"id":62,"name":63,"description":64,"extendedDescription":65,"status":66,"abstraction":67,"structure":68},"CWE-400","Uncontrolled Resource Consumption","The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.","Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.\nThere are at least three distinct scenarios which can commonly lead to resource exhaustion:\nResource exhaustion problems are often result due to an incorrect implementation of the following situations:","Draft","Class","Simple",{"id":70,"name":71,"description":72,"extendedDescription":73,"status":74,"abstraction":75,"structure":68},"CWE-770","Allocation of Resources Without Limits or Throttling","The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.","Code frequently has to work with limited resources, so programmers must be careful to ensure that resources are not consumed too quickly, or too easily.  Without use of quotas, resource limits, or other protection mechanisms, it can be easy for an attacker to consume many resources by rapidly making many requests, or causing larger resources to be used than is needed. When too many resources are allocated, or if a single resource is too large, then it can prevent the code from working correctly, possibly leading to a denial of service.","Incomplete","Base",2,false,[],{"title":80,"metaDescription":81,"keywords":82,"canonicalUrl":83,"structuredData":84},"What is CVE-2024-22164? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2024-22164, a medium severity cyber security vulnerability from 2024. In Splunk Enterprise Security (ES) versions below 7.1.2, ...","CVE-2024-22164, CVE-2024-22164 vulnerability, CVE-2024-22164 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, splunk security, enterprise_security vulnerability","\u002Fwhat-is\u002Fcve-2024-22164",{"@context":85,"@type":86,"headline":80,"description":81,"datePublished":10,"dateModified":11,"author":87,"publisher":91,"about":95,"mainEntityOfPage":99,"articleSection":102,"keywords":103},"https:\u002F\u002Fschema.org","TechArticle",{"@type":88,"name":89,"url":90},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":88,"name":89,"url":90,"logo":92},{"@type":93,"url":94},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":96,"name":6,"description":97,"additionalType":98},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":100,"@id":101},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2024-22164","Cybersecurity","CVE-2024-22164, CVE-2024-22164 vulnerability, CVE-2024-22164 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[105],{"Operator":26,"Negate":26,"Nodes":106},[107],{"Operator":108,"Negate":77,"CPEMatch":109},"OR",[110],{"Vulnerable":4,"Criteria":44,"MatchCriteriaID":111,"VersionStartExcluding":26,"VersionStartIncluding":112,"VersionEndExcluding":113,"VersionEndIncluding":26},"2D79C40D-51D3-4A7E-A3FC-F8638D1E6AFA","7.1.0","7.1.2",[],[],{"lastModified":11,"cacheTime":117,"version":118},1792246390498,"2.0",{"score":120,"band":121,"action":122,"scoredAt":123},17,"Info","Track","2026-10-16T07:00:24.825228+00:00"]