[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-B6k1t5LQ25yewoYcSa9Li9DaxnYwtgLWiQ9vJfoCFM":3,"g5a-risk:CVE-2023-5043":133},{"success":4,"data":5,"meta":130},true,{"cveId":6,"title":7,"description":8,"shortDescription":8,"publishedDate":9,"lastModified":10,"cvssScore":11,"cvssVector":12,"cvssMetrics":13,"epssScore":35,"epssPercentile":27,"epssTimeSeries":36,"severity":37,"affectedProducts":38,"affectedProductsCount":44,"references":45,"referencesCount":75,"weaknesses":76,"weaknessesCount":91,"isActivelyExploited":92,"cisaInfo":27,"otxData":27,"relatedBlogPosts":93,"seoMetadata":94,"configurations":119,"relatedVendorCves":128,"notableEvents":129},"CVE-2023-5043","What is CVE-2023-5043?","Ingress nginx annotation injection causes arbitrary command execution.","2023-10-25T20:15:18.037","2025-02-13T18:15:54.603",8.8,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":14,"CVSSMetricV30":27,"CVSSMetricV2":27,"CVSSMetricV40":27},[15,30],{"Source":16,"Type":17,"CVSSData":18,"ExploitabilityScore":28,"ImpactScore":29},"jordan@liggitt.net","Secondary",{"Version":19,"VectorString":20,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":22,"AvailabilityImpact":22,"BaseScore":26,"BaseSeverity":25,"ExploitCodeMaturity":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"TemporalSeverity":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":22,"ModifiedAttackVector":27,"ModifiedAttackComplexity":27,"ModifiedPrivilegesRequired":27,"ModifiedUserInteraction":27,"ModifiedScope":27,"ModifiedConfidentialityImpact":27,"ModifiedIntegrityImpact":27,"ModifiedAvailabilityImpact":27,"EnvironmentalScore":27,"EnvironmentalSeverity":27},"3.1","CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:L\u002FA:L","NETWORK","LOW","NONE","UNCHANGED","HIGH",7.6,null,2.8,4.7,{"Source":31,"Type":32,"CVSSData":33,"ExploitabilityScore":28,"ImpactScore":34},"nvd@nist.gov","Primary",{"Version":19,"VectorString":12,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":11,"BaseSeverity":25,"ExploitCodeMaturity":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"TemporalSeverity":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":25,"ModifiedAttackVector":27,"ModifiedAttackComplexity":27,"ModifiedPrivilegesRequired":27,"ModifiedUserInteraction":27,"ModifiedScope":27,"ModifiedConfidentialityImpact":27,"ModifiedIntegrityImpact":27,"ModifiedAvailabilityImpact":27,"EnvironmentalScore":27,"EnvironmentalSeverity":27},5.9,0.02234,[35,35,35,35,35,35,35],"High",[39],{"vendor":40,"product":41,"version":42,"criteria":43,"vulnerable":4},"kubernetes","ingress-nginx","*","cpe:2.3:a:kubernetes:ingress-nginx:*:*:*:*:*:*:*:*",1,[46,52,59,63,67,69,71,73],{"url":47,"source":48,"tags":49},"http:\u002F\u002Fwww.openwall.com\u002Flists\u002Foss-security\u002F2023\u002F10\u002F25\u002F4","Openwall",[50,51],"Mailing List","Third Party Advisory",{"url":53,"source":54,"tags":55},"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fingress-nginx\u002Fissues\u002F10571","GitHub",[56,57,58],"Issue Tracking","Mitigation","Vendor Advisory",{"url":60,"source":61,"tags":62},"https:\u002F\u002Fgroups.google.com\u002Fg\u002Fkubernetes-security-announce\u002Fc\u002FpVsXsOpxYZo","Google",[50,57],{"url":64,"source":65,"tags":66},"https:\u002F\u002Fsecurity.netapp.com\u002Fadvisory\u002Fntap-20240307-0012\u002F","Netapp",[],{"url":47,"source":48,"tags":68},[50,51],{"url":53,"source":54,"tags":70},[56,57,58],{"url":60,"source":61,"tags":72},[50,57],{"url":64,"source":65,"tags":74},[],8,[77,85],{"id":78,"name":79,"description":80,"extendedDescription":81,"status":82,"abstraction":83,"structure":84},"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","Class","Simple",{"id":86,"name":87,"description":88,"extendedDescription":89,"status":90,"abstraction":83,"structure":84},"CWE-74","Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')","The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.","Software or other automated logic has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features that classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.","Incomplete",2,false,[],{"title":95,"metaDescription":96,"keywords":97,"canonicalUrl":98,"structuredData":99},"What is CVE-2023-5043? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2023-5043, a high severity cyber security vulnerability from 2023. Ingress nginx annotation injection causes arbitrary command ...","CVE-2023-5043, CVE-2023-5043 vulnerability, CVE-2023-5043 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2023, CVSS score, exploit, patch, remediation, kubernetes security, ingress-nginx vulnerability","\u002Fwhat-is\u002Fcve-2023-5043",{"@context":100,"@type":101,"headline":95,"description":96,"datePublished":9,"dateModified":10,"author":102,"publisher":106,"about":110,"mainEntityOfPage":114,"articleSection":117,"keywords":118},"https:\u002F\u002Fschema.org","TechArticle",{"@type":103,"name":104,"url":105},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":103,"name":104,"url":105,"logo":107},{"@type":108,"url":109},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":111,"name":6,"description":112,"additionalType":113},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":115,"@id":116},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2023-5043","Cybersecurity","CVE-2023-5043, CVE-2023-5043 vulnerability, CVE-2023-5043 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[120],{"Operator":27,"Negate":27,"Nodes":121},[122],{"Operator":123,"Negate":27,"CPEMatch":124},"OR",[125],{"Vulnerable":4,"Criteria":43,"MatchCriteriaID":126,"VersionStartExcluding":27,"VersionStartIncluding":27,"VersionEndExcluding":127,"VersionEndIncluding":27},"B1FAA6D4-954E-4E5F-AB9A-61E1A3F9CD9B","1.9.0",[],[],{"lastModified":10,"cacheTime":131,"version":132},1792248914226,"2.0",{"score":134,"band":135,"action":136,"scoredAt":137},50,"Medium","Plan remediation","2026-10-16T06:59:33.686082+00:00"]