Deepinfer
Monthly
DeepInfer through 0.1.0 ships a profiling HTTP server whose unauthenticated /profile endpoint accepts an attacker-supplied output_dir and writes Chrome trace files to that location, letting remote attackers create directories anywhere the process can reach. Because pre-patch builds bound the server to 0.0.0.0, accepted GET requests, and merged URL query parameters into the request body, a cross-site request from an operator's browser (an <img> or auto-submitting <form>) is enough to trigger collection and force writes; the resulting error messages also act as a filesystem-existence oracle. Impact is bounded to directory creation, disk or inode exhaustion through trace output, and low-confidentiality path disclosure - no code execution is involved, exploitation requires the profiler HTTP server to be running and reachable, and no public exploit code was identified at time of analysis, with no CISA KEV listing.
DeepInfer through 0.1.0 ships a profiling HTTP server whose unauthenticated /profile endpoint accepts an attacker-supplied output_dir and writes Chrome trace files to that location, letting remote attackers create directories anywhere the process can reach. Because pre-patch builds bound the server to 0.0.0.0, accepted GET requests, and merged URL query parameters into the request body, a cross-site request from an operator's browser (an <img> or auto-submitting <form>) is enough to trigger collection and force writes; the resulting error messages also act as a filesystem-existence oracle. Impact is bounded to directory creation, disk or inode exhaustion through trace output, and low-confidentiality path disclosure - no code execution is involved, exploitation requires the profiler HTTP server to be running and reachable, and no public exploit code was identified at time of analysis, with no CISA KEV listing.