oasdiff Vulnerability: SSRF and Local File Read Risks
oasdiff versions from v1.13.2 through v1.18.0 reportedly do not enforce --allow-external-refs=false on the git-revision load path, which may lead to SSRF and local file read vulnerabilities.
What happened
From v1.13.2 through v1.18.0, oasdiff appears to not enforce the --allow-external-refs=false setting on the git-revision load path. This misconfiguration is under investigation for potentially enabling SSRF (Server-Side Request Forgery) and local file read vulnerabilities. Versions v1.18.1 and above are reported to enforce the external-refs policy correctly on the git-revision path.
To assess your exposure, check if your deployment uses oasdiff in the affected version range and if it processes untrusted specifications with external refs disabled. If so, consider upgrading to v1.18.1 or avoid using the git-revision input form when handling such specifications.
For more detailed information, consult the primary sources provided. The situation is still under investigation, and further details may emerge.
How 0Day mitigates this
oasdiff is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.