<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:capev2:capev2:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3acapev2capev2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sun, 13 Sep 2026 11:25:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3acapev2capev2/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Insecure Direct Object Reference in CAPEv2 REST API</title><link>https://feed.craftedsignal.io/briefs/2026-09-capev2-idor/</link><pubDate>Sun, 13 Sep 2026 11:25:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-capev2-idor/</guid><description>CAPEv2 versions up to commit 471ee4b contain an IDOR vulnerability allowing authenticated users to access and delete arbitrary analysis tasks.</description><content:encoded><![CDATA[<p>CAPEv2 up to commit 471ee4b contains an insecure direct object reference (IDOR) vulnerability within its REST API endpoints. The software fails to implement proper ownership validation checks for analysis tasks. Consequently, any authenticated user can bypass access controls to enumerate, read, and delete analysis tasks submitted by other users. This vulnerability is significant in shared sandbox environments where multiple researchers or analysts utilize the same CAPEv2 instance, as it allows for unauthorized data exfiltration or the destruction of historical analysis evidence. Defenders should restrict access to the REST API and monitor for suspicious enumeration patterns or unauthorized deletion requests.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows authenticated users to enumerate all tasks within the system and delete arbitrary analyses. This results in loss of integrity for sandbox reporting and unauthorized access to sensitive malware analysis results.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Update CAPEv2 to a commit after 471ee4b to ensure task ownership validation is enforced. Implement strict access control lists on the REST API endpoint and monitor web server access logs for anomalous patterns in URL parameters associated with task IDs.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>webserver</category><category>idor</category><category>api-security</category></item></channel></rss>