Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sandbox video decoder #171

Open
serpilliere opened this issue Apr 13, 2023 · 0 comments
Open

Sandbox video decoder #171

serpilliere opened this issue Apr 13, 2023 · 0 comments
Labels
hardening Code hardening

Comments

@serpilliere
Copy link
Contributor

In the scenario in which the host runs the Sanzu server, the attacker may also control the video encoder.
In this case, on the client side, the video decoder may receive a video stream data controlled by the attacker.

The client decoder code may be split out of the main code in order to sandbox it.

  • A shared memory to hold raw pixel may be used between the client code and the video decoder
  • a communication between the video decoder and the main code can be used (using also protobuf)

In this case, the video decoder may sandbox itself before parsing arbitrary data.
Moreover, the video decoder could be forced to use software decoding: this will avoid having allowing the use of graphic drivers in the video decoder sandbox. As the decoding process is light compared to the encoding part, this may be acceptable from a performance point of view. (about half a cpu for the 1080p@25fps)

@serpilliere serpilliere added the hardening Code hardening label Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hardening Code hardening
Projects
None yet
Development

No branches or pull requests

1 participant