SurrealDB before 2.3.6 deny-net Bypass via DNS Resolution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.6, 2.3.6, 2.1.8, 3.0.0-alpha.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SurrealDB before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier) fails to validate DNS-resolved hostnames against --deny-net network access restrictions in its http::* functions. An authenticated user can invoke http::<fn>(<url>) with a hostname that resolves to a denied IP address, causing the server to issue the request anyway and return the response. This bypasses network access controls, allowing access to restricted internal endpoints and potentially retrieving or altering sensitive information and credentials, depending on the deployment.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- surrealdb surrealdb
through 2.1.7; From 2.2.0 · fixed in 2.2.6; From 2.3.0 · fixed in 2.3.6; From 3.0.0-alpha.1 · through 3.0.0-alpha.7
- SurrealDBcrates.io
From 2.1.0 · fixed in 2.1.8
- SurrealDBcrates.io
From 2.2.0 · fixed in 2.2.6
- SurrealDBcrates.io
From 3.0.0-alpha.1 · fixed in 3.0.0-alpha.7
- SurrealDBcrates.io
From 2.3.0 · fixed in 2.3.6