[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCOcg3WVRtOxVwgvhAn8rEfNVQ7JRih-9yVfLIEDlkzg":3,"g5a-risk:CVE-2022-1471":161},{"success":4,"data":5,"meta":159},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":38,"epssPercentile":28,"epssTimeSeries":39,"severity":40,"affectedProducts":41,"affectedProductsCount":47,"references":48,"referencesCount":103,"weaknesses":104,"weaknessesCount":120,"isActivelyExploited":121,"cisaInfo":28,"otxData":28,"relatedBlogPosts":122,"seoMetadata":123,"configurations":148,"relatedVendorCves":157,"notableEvents":158},"CVE-2022-1471","What is CVE-2022-1471?","SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.","SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker ...","2022-12-01T11:15:10.553","2025-02-13T17:15:35.627",9.8,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":28,"CVSSMetricV2":28,"CVSSMetricV40":28},[16,31],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":29,"ImpactScore":30},"cve-coordination@google.com","Secondary",{"Version":20,"VectorString":21,"AttackVector":22,"AttackComplexity":23,"PrivilegesRequired":23,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":26,"IntegrityImpact":26,"AvailabilityImpact":23,"BaseScore":27,"BaseSeverity":26,"ExploitCodeMaturity":28,"RemediationLevel":28,"ReportConfidence":28,"TemporalScore":28,"TemporalSeverity":28,"ConfidentialityRequirement":28,"IntegrityRequirement":28,"AvailabilityRequirement":23,"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:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:L","NETWORK","LOW","NONE","UNCHANGED","HIGH",8.3,null,2.8,5.5,{"Source":32,"Type":33,"CVSSData":34,"ExploitabilityScore":36,"ImpactScore":37},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":22,"AttackComplexity":23,"PrivilegesRequired":24,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":26,"IntegrityImpact":26,"AvailabilityImpact":26,"BaseScore":12,"BaseSeverity":35,"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},"CRITICAL",3.9,5.9,0.99569,[38,38,38,38,38,38,38],"Critical",[42],{"vendor":43,"product":44,"version":45,"criteria":46,"vulnerable":4},"snakeyaml_project","snakeyaml","*","cpe:2.3:a:snakeyaml_project:snakeyaml:*:*:*:*:*:*:*:*",1,[49,53,57,63,68,71,75,79,82,85,87,89,91,93,95,97,99,101],{"url":50,"source":51,"tags":52},"http:\u002F\u002Fpacketstormsecurity.com\u002Ffiles\u002F175095\u002FPyTorch-Model-Server-Registration-Deserialization-Remote-Code-Execution.html","Packetstormsecurity",[],{"url":54,"source":55,"tags":56},"http:\u002F\u002Fwww.openwall.com\u002Flists\u002Foss-security\u002F2023\u002F11\u002F19\u002F1","Openwall",[],{"url":58,"source":59,"tags":60},"https:\u002F\u002Fbitbucket.org\u002Fsnakeyaml\u002Fsnakeyaml\u002Fissues\u002F561\u002Fcve-2022-1471-vulnerability-in#comment-64581479","Bitbucket",[61,62],"Issue Tracking","Third Party Advisory",{"url":64,"source":65,"tags":66},"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsecurity-research\u002Fsecurity\u002Fadvisories\u002FGHSA-mjmj-j48q-9wg2","GitHub",[67,62],"Exploit",{"url":69,"source":65,"tags":70},"https:\u002F\u002Fgithub.com\u002Fmbechler\u002Fmarshalsec",[67,62],{"url":72,"source":73,"tags":74},"https:\u002F\u002Fgroups.google.com\u002Fg\u002Fkubernetes-security-announce\u002Fc\u002FmwrakFaEdnc","Google",[],{"url":76,"source":77,"tags":78},"https:\u002F\u002Fsecurity.netapp.com\u002Fadvisory\u002Fntap-20230818-0015\u002F","Netapp",[],{"url":80,"source":77,"tags":81},"https:\u002F\u002Fsecurity.netapp.com\u002Fadvisory\u002Fntap-20240621-0006\u002F",[],{"url":83,"source":65,"tags":84},"https:\u002F\u002Fwww.github.com\u002Fmbechler\u002Fmarshalsec\u002Fblob\u002Fmaster\u002Fmarshalsec.pdf?raw=true",[67,62],{"url":50,"source":51,"tags":86},[],{"url":54,"source":55,"tags":88},[],{"url":58,"source":59,"tags":90},[61,62],{"url":64,"source":65,"tags":92},[67,62],{"url":69,"source":65,"tags":94},[67,62],{"url":72,"source":73,"tags":96},[],{"url":76,"source":77,"tags":98},[],{"url":80,"source":77,"tags":100},[],{"url":83,"source":65,"tags":102},[67,62],18,[105,113],{"id":106,"name":107,"description":108,"extendedDescription":109,"status":110,"abstraction":111,"structure":112},"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":114,"name":115,"description":116,"extendedDescription":117,"status":118,"abstraction":119,"structure":112},"CWE-502","Deserialization of Untrusted Data","The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.","It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security -- which is a dangerous security assumption.\nData that is untrusted can not be trusted to be well-formed.\nWhen developers place no restrictions on \"gadget chains,\" or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.","Draft","Base",2,false,[],{"title":124,"metaDescription":125,"keywords":126,"canonicalUrl":127,"structuredData":128},"What is CVE-2022-1471? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2022-1471, a critical severity cyber security vulnerability from 2022. High exploit probability (99.6%). SnakeYaml's Constructo...","CVE-2022-1471, CVE-2022-1471 vulnerability, CVE-2022-1471 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, snakeyaml_project security, snakeyaml vulnerability, high risk vulnerability, actively exploited, exploit available","\u002Fwhat-is\u002Fcve-2022-1471",{"@context":129,"@type":130,"headline":124,"description":125,"datePublished":10,"dateModified":11,"author":131,"publisher":135,"about":139,"mainEntityOfPage":143,"articleSection":146,"keywords":147},"https:\u002F\u002Fschema.org","TechArticle",{"@type":132,"name":133,"url":134},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":132,"name":133,"url":134,"logo":136},{"@type":137,"url":138},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":140,"name":6,"description":141,"additionalType":142},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":144,"@id":145},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2022-1471","Cybersecurity","CVE-2022-1471, CVE-2022-1471 vulnerability, CVE-2022-1471 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[149],{"Operator":28,"Negate":28,"Nodes":150},[151],{"Operator":152,"Negate":28,"CPEMatch":153},"OR",[154],{"Vulnerable":4,"Criteria":46,"MatchCriteriaID":155,"VersionStartExcluding":28,"VersionStartIncluding":28,"VersionEndExcluding":156,"VersionEndIncluding":28},"3598DC3A-DDD1-4A0B-ACDA-406B85A1EA1A","2.0",[],[],{"lastModified":11,"cacheTime":160,"version":156},1792186563485,{"score":162,"band":163,"action":164,"scoredAt":165},82,"High","Patch now","2026-10-16T06:56:23.303904+00:00"]