HackerOne Disclosed Reports - 2026-11-15

0 Replies, 12 Views

Logo
High
resolved

Unauthenticated remote process termination of Arc RPC nodes via custom JS tracer (Boa engine) leads to sustained node DoS


Bug reported by Cantina was disclosed at November 15, 2026, 2:35 pm   |   Uncontrolled Resource Consumption

A vulnerability was discovered in public blockchain RPC endpoints where custom JavaScript tracers were exposed without authentication or execution limits. The embedded JavaScript engine lacked wall-clock timeouts, memory caps, result-size limits, and process isolation.

Multiple independent attack vectors were identified that could remotely terminate the RPC node process or exhaust its resources. These included parser stack overflow causing process abort, a garbage collection borrow error triggering non-unwinding panic, regular expression engine backtracking without limits causing thread exhaustion, and host-level functions that iterated over attacker-controlled array lengths in native code outside the JavaScript loop limit constraints.

Response amplification was also possible, with no caps on result sizes returned to clients. The existing JavaScript iteration and recursion limits could be bypassed through native code execution paths, and panic containment only worked for unwinding panics, not fatal runtime errors like stack overflows.

The vulnerabilities were confirmed against live endpoints through proof-of-concept testing demonstrating process termination, worker thread exhaustion, and memory exhaustion from single HTTP requests. The attack surface was further expanded by lack of rate limiting and arbitrary origin reflection in cross-origin requests.


Logo
Medium
resolved

Anonymous API Rate Limit Bypass via X-Forwarded-For


Bug reported by hexafaton was disclosed at November 15, 2026, 7:28 am   |   Uncontrolled Resource Consumption

Weblate's anonymous API rate limiting was found to be vulnerable to bypass through manipulation of proxy headers. The affected throttling class did not properly override client identification, allowing it to inherit Django REST Framework's default behavior which was influenced by untrusted request headers. An unauthenticated client could supply different proxy header values between requests to obtain separate rate-limit buckets instead of being associated with a single client identity. This weakness was observed across multiple anonymous API endpoints and allowed more requests than the configured per-client limit. A fix was proposed that explicitly uses server-side client address information for throttle identity instead of allowing request headers to determine anonymous rate-limit buckets.


Logo
Low
resolved

Anonymous Translation Suggestion IP Address Exposure Through Change API


Bug reported by 4upasta was disclosed at November 15, 2026, 6:57 am   |   Information Disclosure

A vulnerability was identified where the IP address associated with anonymous translation suggestions was exposed through the Change API to authenticated users with read-only project access. The IP address was stored in change details and returned by the API, but was not displayed in the regular change-history interface. The issue was confirmed in local testing against a specific commit version. No live servers or real user data were involved in the testing.


Logo
Critical
resolved

Privilege escalation via unfiltered role restoration in project backup import


Bug reported by Zukosdead was disclosed at November 15, 2026, 5:16 am   |   Privilege Escalation

A privilege escalation vulnerability was discovered in project backup import functionality. When restoring access-control teams from backup files, roles carrying global site-wide permissions were not validated and could be attached to project-scoped teams without proper filtering. This allowed users with limited backup import privileges to gain unauthorized site-wide permissions. Additionally, a separate issue in the permissions collection logic failed to exclude project-scoped team memberships when determining global permissions, allowing the escalated privileges to take effect across the entire site. The vulnerability was confirmed through multiple reproduction tests demonstrating that low-privilege users could obtain administrative capabilities after importing a crafted backup file.


[Image: e72398fe92beda2aa80d0329e8b9f4febece7568.gif]



Users browsing this thread: 1 Guest(s)