CyberRota Analysis
AI-GeneratedThe next-video library for Next.js applications prior to version 2.8.1 is vulnerable due to an unauthenticated URL query parameter in its GET endpoint, allowing remote attackers to exploit directory traversal and read sensitive JSON files from the application’s file system. This could expose critical information such as encryption materials and configuration details, potentially compromising the application's security. Developers using next-video should prioritize upgrading to version 2.8.1 to mitigate this risk, especially if their applications expose the runtime request handler.
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
next-video is a library for adding video to Next.js applications. Prior to 2.8.1, the GET endpoint exported by next-video/request-handler and commonly mounted at /api/video accepts an unauthenticated url query parameter, while src/utils/utils.ts isRemote() treats any value without an HTTP or HTTPS prefix as a local path. src/request-handler.ts passes that value through src/assets.ts getAssetPath() to src/config.ts loadAsset(), which appends a JSON suffix and uses fs.readFile without canonicalizing the path or verifying that it remains inside the configured video folder. A remote attacker can therefore escape the intended asset directory and read JSON files accessible to the application process, including Next.js server-action encryption material, preview-mode keys, build manifests, route metadata, absolute paths, and application video asset identifiers. Applications that do not expose the runtime request handler are not affected through this route. This issue is fixed in version 2.8.1.