CyberRota Analysis
AI-GeneratedBudibase versions prior to 3.40.0 are vulnerable to a DNS rebinding attack that allows an attacker to manipulate outbound REST API calls, potentially redirecting them to internal addresses and gaining unauthorized access to sensitive data. This flaw arises from improper handling of validated addresses in the outbound fetch process, which can lead to full response access and execution of arbitrary REST methods. Organizations using Budibase should prioritize upgrading to version 3.40.0 to mitigate the risk of exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Budibase is an open-source low-code platform. Prior to 3.40.0, packages/backend-core/src/utils/outboundFetch.ts pinned a validated address through a Node agent, but the REST integration used getDispatcher from packages/backend-core/src/utils/fetch.ts, causing undici to ignore that agent and resolve the hostname again. A builder could use DNS rebinding to make packages/server/src/integrations/rest.ts connect to an internal address after a public address passed validation, with full response access and arbitrary REST methods. The fix adds createPinnedLookup support to the undici dispatcher and passes the validated address to custom fetch implementations. This issue is fixed in version 3.40.0.