[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fxHWsd-x9tmd5lnbFUaTmD8WNBE2S4zfHxBN8ahJbgvU":3,"g5a-risk:CVE-2023-42457":132},{"success":4,"data":5,"meta":129},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":45,"references":46,"referencesCount":73,"weaknesses":74,"weaknessesCount":45,"isActivelyExploited":90,"cisaInfo":26,"otxData":26,"relatedBlogPosts":91,"seoMetadata":92,"configurations":117,"relatedVendorCves":127,"notableEvents":128},"CVE-2023-42457","What is CVE-2023-42457?","plone.rest allows users to use HTTP verbs such as GET, POST, PUT, DELETE, etc. in Plone. Starting in the 2.x branch and prior to versions 2.0.1 and 3.0.1, when the `++api++` traverser is accidentally used multiple times in a url, handling it takes increasingly longer, making the server less responsive. Patches are available in `plone.rest` 2.0.1 and 3.0.1.  Series 1.x is not affected. As a workaround, one may redirect `\u002F++api++\u002F++api++` to `\u002F++api++` in one's frontend web server (nginx, Apache).","plone.rest allows users to use HTTP verbs such as GET, POST, PUT, DELETE, etc. in Plone. Starting in the 2.x branch and prior to versions 2.0.1 and 3.0.1, wh...","2023-09-21T15:15:10.943","2025-02-13T17:17:08.29",7.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":26,"CVSSMetricV40":26},[16,29],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"security-advisories@github.com","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"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,3.9,3.6,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"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.01013,[33,33,33,33,33,33,33],"High",[37,42],{"vendor":38,"product":39,"version":40,"criteria":41,"vulnerable":4},"plone","rest","2.0.0","cpe:2.3:a:plone:rest:2.0.0:*:*:*:*:*:*:*",{"vendor":38,"product":39,"version":43,"criteria":44,"vulnerable":4},"3.0.0","cpe:2.3:a:plone:rest:3.0.0:*:*:*:*:*:*:*",2,[47,53,58,61,65,67,69,71],{"url":48,"source":49,"tags":50},"http:\u002F\u002Fwww.openwall.com\u002Flists\u002Foss-security\u002F2023\u002F09\u002F22\u002F2","Openwall",[51,52],"Mailing List","Third Party Advisory",{"url":54,"source":55,"tags":56},"https:\u002F\u002Fgithub.com\u002Fplone\u002Fplone.rest\u002Fcommit\u002F43b4a7e86206e237e1de5ca3817ed071575882f7","GitHub",[57],"Patch",{"url":59,"source":55,"tags":60},"https:\u002F\u002Fgithub.com\u002Fplone\u002Fplone.rest\u002Fcommit\u002F77846a9842889b24f35e8bedc2e9d461388d3302",[57],{"url":62,"source":55,"tags":63},"https:\u002F\u002Fgithub.com\u002Fplone\u002Fplone.rest\u002Fsecurity\u002Fadvisories\u002FGHSA-h6rp-mprm-xgcq",[64],"Vendor Advisory",{"url":48,"source":49,"tags":66},[51,52],{"url":54,"source":55,"tags":68},[57],{"url":59,"source":55,"tags":70},[57],{"url":62,"source":55,"tags":72},[64],8,[75,83],{"id":76,"name":77,"description":78,"extendedDescription":79,"status":80,"abstraction":81,"structure":82},"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":84,"name":85,"description":86,"extendedDescription":87,"status":88,"abstraction":89,"structure":82},"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",false,[],{"title":93,"metaDescription":94,"keywords":95,"canonicalUrl":96,"structuredData":97},"What is CVE-2023-42457? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2023-42457, a high severity cyber security vulnerability from 2023. plone.rest allows users to use HTTP verbs such as GET, POST...","CVE-2023-42457, CVE-2023-42457 vulnerability, CVE-2023-42457 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, plone security, rest vulnerability","\u002Fwhat-is\u002Fcve-2023-42457",{"@context":98,"@type":99,"headline":93,"description":94,"datePublished":10,"dateModified":11,"author":100,"publisher":104,"about":108,"mainEntityOfPage":112,"articleSection":115,"keywords":116},"https:\u002F\u002Fschema.org","TechArticle",{"@type":101,"name":102,"url":103},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":101,"name":102,"url":103,"logo":105},{"@type":106,"url":107},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":109,"name":6,"description":110,"additionalType":111},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":113,"@id":114},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2023-42457","Cybersecurity","CVE-2023-42457, CVE-2023-42457 vulnerability, CVE-2023-42457 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[118],{"Operator":26,"Negate":26,"Nodes":119},[120],{"Operator":121,"Negate":26,"CPEMatch":122},"OR",[123,125],{"Vulnerable":4,"Criteria":41,"MatchCriteriaID":124,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"5CD311A9-2185-4CC1-9FDB-8EB5F33DEB07",{"Vulnerable":4,"Criteria":44,"MatchCriteriaID":126,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"73CAED86-5DE2-49CD-9AF0-5DB6C73670B3",[],[],{"lastModified":11,"cacheTime":130,"version":131},1792266320493,"2.0",{"score":133,"band":134,"action":135,"scoredAt":136},46,"Medium","Plan remediation","2026-10-16T06:59:11.9721+00:00"]