3 ms·
>When received by the sensor and loaded into the Content Interpreter, problematic content in Channel File 291 resulted in an out-of-bounds memory read triggerin
by 1970-01-01 2y ago
>When received by the sensor and loaded into the Content Interpreter, problematic content in Channel File 291 resulted in an out-of-bounds memory read triggering an exception.
Wasn't 'Channel File 291' a garbage file filled with null pointers? Meaning it's problematic content in the same way as filling your parachute bag with ice cream and screws is problematic.
- hyperpape 2y agoThey specifically denied that null bytes were the issue in an earlier update. https://www.crowdstrike.com/blog/falcon-update-for-windows-hosts-technical-details/ https://www.crowdstrike.com/blog/falcon-update-for-windows-h...
- 1970-01-01 2y agoNull pointers, not a null array
- hyperpape 2y agoI'm not sure what you're saying, but note that a file fundamentally cannot contain a null pointer, a file can just contain various bytes.