CyberRota Analysis
AI-GeneratedThe guard checker in Rocq Prover is vulnerable due to its failure to properly track recursive calls made through fixpoint arguments, allowing for the creation of a type that is definitionally equal to its own negation. This can lead to logical inconsistencies, producing false results in purely definitional code without the need for tactics or unsafe flags. Users of Rocq Prover, particularly those relying on higher-order functions, should prioritize updating to version 9.2.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint's own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.