[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f296sw8QuFx0ZnMWClBtc4GuQxTE_ly0z_IyUyO8GuQ0":3,"g5a-risk:CVE-2022-31079":128},{"success":4,"data":5,"meta":126},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":47,"epssPercentile":27,"epssTimeSeries":48,"severity":49,"affectedProducts":50,"affectedProductsCount":56,"references":57,"referencesCount":56,"weaknesses":63,"weaknessesCount":79,"isActivelyExploited":80,"cisaInfo":27,"otxData":27,"relatedBlogPosts":81,"seoMetadata":82,"configurations":107,"relatedVendorCves":124,"notableEvents":125},"CVE-2022-31079","What is CVE-2022-31079?","KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service. Only an authenticated user can cause this issue. It will be affected only when users enable `cloudStream` module in the config file `cloudcore.yaml` and enable `edgeStream` module in the config file `edgecore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable cloudStream module in the config file `cloudcore.yaml` and disable edgeStream module in the config file `edgecore.yaml`.","KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10....","2022-07-11T21:15:08.327","2023-07-21T17:07:51.707",6.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":27,"CVSSMetricV2":37,"CVSSMetricV40":27},[16,30],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":28,"ImpactScore":29},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":26,"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},"3.1","NETWORK","LOW","NONE","UNCHANGED","HIGH","MEDIUM",null,2.8,3.6,{"Source":31,"Type":32,"CVSSData":33,"ExploitabilityScore":36,"ImpactScore":29},"security-advisories@github.com","Secondary",{"Version":20,"VectorString":34,"AttackVector":21,"AttackComplexity":25,"PrivilegesRequired":25,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":25,"BaseScore":35,"BaseSeverity":26,"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},"CVSS:3.1\u002FAV:N\u002FAC:H\u002FPR:H\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:H",4.4,0.7,[38],{"Source":17,"Type":18,"CVSSData":39,"BaseSeverity":22,"ExploitabilityScore":45,"ImpactScore":46,"ACInsufInfo":27,"ObtainAllPrivilege":27,"ObtainUserPrivilege":27,"ObtainOtherPrivilege":27,"UserInteractionRequired":27},{"Version":40,"VectorString":41,"AccessVector":21,"AccessComplexity":26,"Authentication":42,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":43,"BaseScore":44,"BaseSeverity":27,"Exploitability":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"CollateralDamagePotential":27,"TargetDistribution":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":27,"EnvironmentalScore":27},"2.0","AV:N\u002FAC:M\u002FAu:S\u002FC:N\u002FI:N\u002FA:P","SINGLE","PARTIAL",3.5,6.8,2.9,0.00703,[47,47,47,47,47,47,47],"Medium",[51],{"vendor":52,"product":53,"version":54,"criteria":55,"vulnerable":4},"linuxfoundation","kubeedge","*","cpe:2.3:a:linuxfoundation:kubeedge:*:*:*:*:*:*:*:*",1,[58],{"url":59,"source":60,"tags":61},"https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fkubeedge\u002Fsecurity\u002Fadvisories\u002FGHSA-wrcr-x4qj-j543","GitHub",[62],"Third Party Advisory",[64,72],{"id":65,"name":66,"description":67,"extendedDescription":68,"status":69,"abstraction":70,"structure":71},"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","Simple",{"id":73,"name":74,"description":75,"extendedDescription":76,"status":77,"abstraction":78,"structure":71},"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",2,false,[],{"title":83,"metaDescription":84,"keywords":85,"canonicalUrl":86,"structuredData":87},"What is CVE-2022-31079? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2022-31079, a medium severity cyber security vulnerability from 2022. KubeEdge is an open source system for extending native co...","CVE-2022-31079, CVE-2022-31079 vulnerability, CVE-2022-31079 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, linuxfoundation security, kubeedge vulnerability","\u002Fwhat-is\u002Fcve-2022-31079",{"@context":88,"@type":89,"headline":83,"description":84,"datePublished":10,"dateModified":11,"author":90,"publisher":94,"about":98,"mainEntityOfPage":102,"articleSection":105,"keywords":106},"https:\u002F\u002Fschema.org","TechArticle",{"@type":91,"name":92,"url":93},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":91,"name":92,"url":93,"logo":95},{"@type":96,"url":97},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":99,"name":6,"description":100,"additionalType":101},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":103,"@id":104},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2022-31079","Cybersecurity","CVE-2022-31079, CVE-2022-31079 vulnerability, CVE-2022-31079 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[108],{"Operator":27,"Negate":27,"Nodes":109},[110],{"Operator":111,"Negate":27,"CPEMatch":112},"OR",[113,116,120],{"Vulnerable":4,"Criteria":55,"MatchCriteriaID":114,"VersionStartExcluding":27,"VersionStartIncluding":27,"VersionEndExcluding":115,"VersionEndIncluding":27},"3A932E23-CC93-426C-B4D6-90A7D920CB95","1.9.4",{"Vulnerable":4,"Criteria":55,"MatchCriteriaID":117,"VersionStartExcluding":27,"VersionStartIncluding":118,"VersionEndExcluding":119,"VersionEndIncluding":27},"8ABDAE98-2267-449F-9FB0-D7A0536D2DE0","1.10.0","1.10.2",{"Vulnerable":4,"Criteria":55,"MatchCriteriaID":121,"VersionStartExcluding":27,"VersionStartIncluding":122,"VersionEndExcluding":123,"VersionEndIncluding":27},"6D1541C6-7E77-43CC-982C-27768120D625","1.11.0","1.11.1",[],[],{"lastModified":11,"cacheTime":127,"version":40},1792437256782,{"score":129,"band":130,"action":131,"scoredAt":132},23,"Low","Monitor","2026-10-16T06:55:06.481858+00:00"]