[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fbcrt4nHqAUwkaQ5-wkwWHPopD95asmCamHe-Q28geXY":3,"g5a-risk:CVE-2023-42503":117},{"success":4,"data":5,"meta":114},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":31,"epssPercentile":28,"epssTimeSeries":32,"severity":33,"affectedProducts":34,"affectedProductsCount":40,"references":41,"referencesCount":58,"weaknesses":59,"weaknessesCount":74,"isActivelyExploited":75,"cisaInfo":28,"otxData":28,"relatedBlogPosts":76,"seoMetadata":77,"configurations":102,"relatedVendorCves":112,"notableEvents":113},"CVE-2023-42503","What is CVE-2023-42503?","Improper Input Validation, Uncontrolled Resource Consumption vulnerability in Apache Commons Compress in TAR parsing.This issue affects Apache Commons Compress: from 1.22 before 1.24.0.\n\nUsers are recommended to upgrade to version 1.24.0, which fixes the issue.\n\nA third party can create a malformed TAR file by manipulating file modification times headers, which when parsed with Apache Commons Compress, will cause a denial of service issue via CPU consumption.\n\nIn version 1.22 of Apache Commons Compress, support was added for file modification times with higher precision (issue # COMPRESS-612 [1]). The format for the PAX extended headers carrying this data consists of two numbers separated by a period [2], indicating seconds and subsecond precision (for example “1647221103.5998539”). The impacted fields are “atime”, “ctime”, “mtime” and “LIBARCHIVE.creationtime”. No input validation is performed prior to the parsing of header values.\n\nParsing of these numbers uses the BigDecimal [3] class from the JDK which has a publicly known algorithmic complexity issue when doing operations on large numbers, causing denial of service (see issue # JDK-6560193 [4]). A third party can manipulate file time headers in a TAR file by placing a number with a very long fraction (300,000 digits) or a number with exponent notation (such as “9e9999999”) within a file modification time header, and the parsing of files with these headers will take hours instead of seconds, leading to a denial of service via exhaustion of CPU resources. This issue is similar to CVE-2012-2098 [5].\n\n[1]:  https:\u002F\u002Fissues.apache.org\u002Fjira\u002Fbrowse\u002FCOMPRESS-612 \n[2]:  https:\u002F\u002Fpubs.opengroup.org\u002Fonlinepubs\u002F9699919799\u002Futilities\u002Fpax.html#tag_20_92_13_05 \n[3]:  https:\u002F\u002Fdocs.oracle.com\u002Fjavase\u002F8\u002Fdocs\u002Fapi\u002Fjava\u002Fmath\u002FBigDecimal.html \n[4]:  https:\u002F\u002Fbugs.openjdk.org\u002Fbrowse\u002FJDK-6560193 \n[5]:  https:\u002F\u002Fcve.mitre.org\u002Fcgi-bin\u002Fcvename.cgi?name=CVE-2012-2098 \n\nOnly applications using CompressorStreamFactory class (with auto-detection of file types), TarArchiveInputStream and TarFile classes to parse TAR files are impacted. Since this code was introduced in v1.22, only that version and later versions are impacted.","Improper Input Validation, Uncontrolled Resource Consumption vulnerability in Apache Commons Compress in TAR parsing.This issue affects Apache Commons Compre...","2023-09-14T08:15:08.057","2025-02-13T17:17:08.72",5.5,"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:N\u002FI:N\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":28,"CVSSMetricV2":28,"CVSSMetricV40":28},[16],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":29,"ImpactScore":30},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":26,"BaseScore":12,"BaseSeverity":27,"ExploitCodeMaturity":28,"RemediationLevel":28,"ReportConfidence":28,"TemporalScore":28,"TemporalSeverity":28,"ConfidentialityRequirement":28,"IntegrityRequirement":28,"AvailabilityRequirement":26,"ModifiedAttackVector":28,"ModifiedAttackComplexity":28,"ModifiedPrivilegesRequired":28,"ModifiedUserInteraction":28,"ModifiedScope":28,"ModifiedConfidentialityImpact":28,"ModifiedIntegrityImpact":28,"ModifiedAvailabilityImpact":28,"EnvironmentalScore":28,"EnvironmentalSeverity":28},"3.1","LOCAL","LOW","NONE","REQUIRED","UNCHANGED","HIGH","MEDIUM",null,1.8,3.6,0.00601,[31,31,31,31,31,31,31],"Medium",[35],{"vendor":36,"product":37,"version":38,"criteria":39,"vulnerable":4},"apache","commons_compress","*","cpe:2.3:a:apache:commons_compress:*:*:*:*:*:*:*:*",1,[42,49,54,56],{"url":43,"source":44,"tags":45},"https:\u002F\u002Flists.apache.org\u002Fthread\u002F5xwcyr600mn074vgxq92tjssrchmc93c","Apache",[46,47,48],"Issue Tracking","Mailing List","URL Repurposed",{"url":50,"source":51,"tags":52},"https:\u002F\u002Fsecurity.netapp.com\u002Fadvisory\u002Fntap-20231020-0003\u002F","Netapp",[53],"Third Party Advisory",{"url":43,"source":44,"tags":55},[46,47,48],{"url":50,"source":51,"tags":57},[53],4,[60,68],{"id":61,"name":62,"description":63,"extendedDescription":64,"status":65,"abstraction":66,"structure":67},"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":69,"name":70,"description":71,"extendedDescription":72,"status":73,"abstraction":66,"structure":67},"CWE-20","Improper Input Validation","The product receives input or data, but it does\n        not validate or incorrectly validates that the input has the\n        properties that are required to process the data safely and\n        correctly.","Input validation is a frequently-used technique\n\t   for checking potentially dangerous inputs in order to\n\t   ensure that the inputs are safe for processing within the\n\t   code, or when communicating with other components.  When\n\t   software does not validate input properly, an attacker is\n\t   able to craft the input in a form that is not expected by\n\t   the rest of the application. This will lead to parts of the\n\t   system receiving unintended input, which may result in\n\t   altered control flow, arbitrary control of a resource, or\n\t   arbitrary code execution.\nInput validation is not the only technique for\n\t   processing input, however.  Other techniques attempt to\n\t   transform potentially-dangerous input into something safe, such\n\t   as filtering (CWE-790) - which attempts to remove dangerous\n\t   inputs - or encoding\u002Fescaping (CWE-116), which attempts to\n\t   ensure that the input is not misinterpreted when it is included\n\t   in output to another component. Other techniques exist as well\n\t   (see CWE-138 for more examples.)\nInput validation can be applied to:\nData can be simple or structured.  Structured data\n\t   can be composed of many nested layers, composed of\n\t   combinations of metadata and raw data, with other simple or\n\t   structured data.\nMany properties of raw data or metadata may need\n\t   to be validated upon entry into the code, such\n\t   as:\nImplied or derived properties of data must often\n\t   be calculated or inferred by the code itself.  Errors in\n\t   deriving properties may be considered a contributing factor\n\t   to improper input validation.\nNote that \"input validation\" has very different\n\t   meanings to different people, or within different\n\t   classification schemes.  Caution must be used when\n\t   referencing this CWE entry or mapping to it.  For example,\n\t   some weaknesses might involve inadvertently giving control\n\t   to an attacker over an input when they should not be able\n\t   to provide an input at all, but sometimes this is referred\n\t   to as input validation.\nFinally, it is important to emphasize that the\n\t   distinctions between input validation and output escaping\n\t   are often blurred, and developers must be careful to\n\t   understand the difference, including how input validation\n\t   is not always sufficient to prevent vulnerabilities,\n\t   especially when less stringent data types must be\n\t   supported, such as free-form text. Consider a SQL injection\n\t   scenario in which a person's last name is inserted into a\n\t   query. The name \"O'Reilly\" would likely pass the validation\n\t   step since it is a common last name in the English\n\t   language. However, this valid name cannot be directly\n\t   inserted into the database because it contains the \"'\"\n\t   apostrophe character, which would need to be escaped or\n\t   otherwise transformed. In this case, removing the\n\t   apostrophe might reduce the risk of SQL injection, but it\n\t   would produce incorrect behavior because the wrong name\n\t   would be recorded.","Stable",2,false,[],{"title":78,"metaDescription":79,"keywords":80,"canonicalUrl":81,"structuredData":82},"What is CVE-2023-42503? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2023-42503, a medium severity cyber security vulnerability from 2023. Improper Input Validation, Uncontrolled Resource Consumpt...","CVE-2023-42503, CVE-2023-42503 vulnerability, CVE-2023-42503 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2023, CVSS score, exploit, patch, remediation, apache security, commons_compress vulnerability","\u002Fwhat-is\u002Fcve-2023-42503",{"@context":83,"@type":84,"headline":78,"description":79,"datePublished":10,"dateModified":11,"author":85,"publisher":89,"about":93,"mainEntityOfPage":97,"articleSection":100,"keywords":101},"https:\u002F\u002Fschema.org","TechArticle",{"@type":86,"name":87,"url":88},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":86,"name":87,"url":88,"logo":90},{"@type":91,"url":92},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":94,"name":6,"description":95,"additionalType":96},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":98,"@id":99},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2023-42503","Cybersecurity","CVE-2023-42503, CVE-2023-42503 vulnerability, CVE-2023-42503 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[103],{"Operator":28,"Negate":28,"Nodes":104},[105],{"Operator":106,"Negate":28,"CPEMatch":107},"OR",[108],{"Vulnerable":4,"Criteria":39,"MatchCriteriaID":109,"VersionStartExcluding":28,"VersionStartIncluding":110,"VersionEndExcluding":111,"VersionEndIncluding":28},"F05475BE-7994-4CCC-A70C-FCBE832D886A","1.22","1.24.0",[],[],{"lastModified":11,"cacheTime":115,"version":116},1792278747457,"2.0",{"score":118,"band":119,"action":120,"scoredAt":121},18,"Info","Track","2026-10-16T06:59:06.346587+00:00"]