datacontract-cli is vulnerable to Server-Side Request Forgery (SSRF)
68
Medium Risk
The datacontract api server accepts a posted data contract and connects to the data sources and URLs that the contract declares. Before the fix, it sends environment-held data source credentials and the platform API key to whatever host the posted contract or publish target names, publishes results to arbitrary URLs, and reads local files through a servers[].type: local entry and an unconfined DuckDB connection. A client that can post a contract can make the server send its secrets to a host the client controls and read files on the server. The fix restricts credential and result delivery to the configured host, refuses local file servers unless explicitly enabled, and confines the DuckDB connection to the declared data locations.
You are affected if you are using a version that falls within the vulnerable range and you run the datacontract api server and expose it to clients that can post data contracts you do not fully trust.
datacontract-cli is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.10.20 - 1.1.1.
Upgrade the datacontract-cli library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.