[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAt2wNHWnlXdYBrlL-rJEgTTlvaTIzUv4HN95k5YNPHM":3,"g5a-risk:CVE-2022-39361":134},{"success":4,"data":5,"meta":131},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":33,"epssPercentile":26,"epssTimeSeries":34,"severity":35,"affectedProducts":36,"affectedProductsCount":41,"references":42,"referencesCount":41,"weaknesses":48,"weaknessesCount":63,"isActivelyExploited":64,"cisaInfo":26,"otxData":26,"relatedBlogPosts":65,"seoMetadata":66,"configurations":91,"relatedVendorCves":129,"notableEvents":130},"CVE-2022-39361","What is CVE-2022-39361?","Metabase is data visualization software. Prior to versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9, H2 (Sample Database) could allow Remote Code Execution (RCE), which can be abused by users able to write SQL queries on H2 databases. This issue is patched in versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9. Metabase no longer allows DDL statements in H2 native queries.","Metabase is data visualization software. Prior to versions 0.44.5, 1.44.5, 0.43.7, 1.43.7, 0.42.6, 1.42.6, 0.41.9, and 1.41.9, H2 (Sample Database) could all...","2022-10-26T19:15:14.707","2022-10-28T16:43:54.66",8.8,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":26,"CVSSMetricV40":26},[16,29],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"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","HIGH",null,2.8,5.9,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"security-advisories@github.com","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},0.01075,[33,33,33,33,33,33,33],"High",[37],{"vendor":38,"product":38,"version":39,"criteria":40,"vulnerable":4},"metabase","*","cpe:2.3:a:metabase:metabase:*:*:*:*:*:*:*:*",1,[43],{"url":44,"source":45,"tags":46},"https:\u002F\u002Fgithub.com\u002Fmetabase\u002Fmetabase\u002Fsecurity\u002Fadvisories\u002FGHSA-gqpj-wcr3-p88v","GitHub",[47],"Third Party Advisory",[49,57],{"id":50,"name":51,"description":52,"extendedDescription":53,"status":54,"abstraction":55,"structure":56},"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":58,"name":59,"description":60,"extendedDescription":61,"status":62,"abstraction":55,"structure":56},"CWE-441","Unintended Proxy or Intermediary ('Confused Deputy')","The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.","If an attacker cannot directly contact a target, but the product has access to the target, then the attacker can send a request to the product and have it be forwarded to the target. The request would appear to be coming from the product's system, not the attacker's system. As a result, the attacker can bypass access controls (such as firewalls) or hide the source of malicious requests, since the requests would not be coming directly from the attacker.\nSince proxy functionality and message-forwarding often serve a legitimate purpose, this issue only becomes a vulnerability when:","Draft",2,false,[],{"title":67,"metaDescription":68,"keywords":69,"canonicalUrl":70,"structuredData":71},"What is CVE-2022-39361? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2022-39361, a high severity cyber security vulnerability from 2022. Metabase is data visualization software. Prior to versions ...","CVE-2022-39361, CVE-2022-39361 vulnerability, CVE-2022-39361 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, metabase security, metabase vulnerability","\u002Fwhat-is\u002Fcve-2022-39361",{"@context":72,"@type":73,"headline":67,"description":68,"datePublished":10,"dateModified":11,"author":74,"publisher":78,"about":82,"mainEntityOfPage":86,"articleSection":89,"keywords":90},"https:\u002F\u002Fschema.org","TechArticle",{"@type":75,"name":76,"url":77},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":75,"name":76,"url":77,"logo":79},{"@type":80,"url":81},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":83,"name":6,"description":84,"additionalType":85},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":87,"@id":88},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2022-39361","Cybersecurity","CVE-2022-39361, CVE-2022-39361 vulnerability, CVE-2022-39361 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[92],{"Operator":26,"Negate":26,"Nodes":93},[94],{"Operator":95,"Negate":26,"CPEMatch":96},"OR",[97,101,105,109,113,117,121,125],{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":98,"VersionStartExcluding":26,"VersionStartIncluding":99,"VersionEndExcluding":100,"VersionEndIncluding":26},"BCD50540-E323-41CE-9D9C-EDA8CB718E42","0.41.0","0.41.9",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":102,"VersionStartExcluding":26,"VersionStartIncluding":103,"VersionEndExcluding":104,"VersionEndIncluding":26},"EF01C7BF-CB4C-4990-9082-587CFD555225","0.42.0","0.42.6",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":106,"VersionStartExcluding":26,"VersionStartIncluding":107,"VersionEndExcluding":108,"VersionEndIncluding":26},"8858058E-C597-4752-8625-9B279DC65A48","0.43.0","0.43.7",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":110,"VersionStartExcluding":26,"VersionStartIncluding":111,"VersionEndExcluding":112,"VersionEndIncluding":26},"6A94F7EA-BC18-4013-9A93-7962226FDD98","0.44.0","0.44.5",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":114,"VersionStartExcluding":26,"VersionStartIncluding":115,"VersionEndExcluding":116,"VersionEndIncluding":26},"804B84E1-5D1A-4251-9829-65F5FD927D99","1.41.0","1.41.9",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":118,"VersionStartExcluding":26,"VersionStartIncluding":119,"VersionEndExcluding":120,"VersionEndIncluding":26},"73310924-8CD4-4696-89B9-EED3390375A6","1.42.0","1.42.6",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":122,"VersionStartExcluding":26,"VersionStartIncluding":123,"VersionEndExcluding":124,"VersionEndIncluding":26},"A86AA0C8-2C4F-4DDD-8371-6B43611E2479","1.43.0","1.43.7",{"Vulnerable":4,"Criteria":40,"MatchCriteriaID":126,"VersionStartExcluding":26,"VersionStartIncluding":127,"VersionEndExcluding":128,"VersionEndIncluding":26},"EF7A60F6-5062-4094-91A5-71445F9B7BC1","1.44.0","1.44.5",[],[],{"lastModified":11,"cacheTime":132,"version":133},1792326724317,"2.0",{"score":135,"band":136,"action":137,"scoredAt":138},48,"Medium","Plan remediation","2026-10-16T06:56:03.692186+00:00"]