Atomic-Server
Atomic Server: Unauthenticated full-response SSRF in Atomic-Server /bookmark endpoint
Atomic Server is an open source headless CMS and real-time database. Prior to 0.40.3, unauthenticated requests to /bookmark can supply a url that server/src/plugins/bookmark.rs passes through fetch_data to fetch_body. Endpoint dispatch in lib/src/db.rs invokes the handler before check_read, and lib/src/client/helpers.rs previously checked only that the URL began with HTTP, without restricting loopback, private, link-local, DNS-rebinding, or redirect targets. The handler reflects fetched content in returned resource fields, making this a full-response server-side request forgery that can expose internal services and plain-GET cloud metadata. The short request timeout limits slow targets, and metadata services requiring a separate token request are outside the demonstrated GET-only path. This issue is fixed in version 0.40.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.40.3
Fixed in 0.40.3
Mitigation
Upgrade atomic-server to 0.40.3 or later.
References
- Vendor advisory github.com/ontola/atomic-server/security/advis…
- Patch github.com/ontola/atomic-server/commit/006ff29…
- Patch github.com/ontola/atomic-server/commit/2d4535f…
2 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.