We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
sqlite is in the news with a vulnerability. An attacker can craft a malicious sqlite DB, which can cause unexpected behavior. https://research.checkpoint.com/select-code_execution-from-using-sqlite/
Several places in osquery read sqlite data.
Does this give a user a route to privilege escalation? It's not yet clear what mitigations we can do.
The text was updated successfully, but these errors were encountered:
The mitigations would be to remove the build-time options here: https://github.com/osquery/third-party-sqlite/blob/2ca13814d05e8408b445b1938aaf6c675e5a510f/CMakeLists.txt#L21
Sorry, something went wrong.
No branches or pull requests
sqlite is in the news with a vulnerability. An attacker can craft a malicious sqlite DB, which can cause unexpected behavior. https://research.checkpoint.com/select-code_execution-from-using-sqlite/
Several places in osquery read sqlite data.
Does this give a user a route to privilege escalation? It's not yet clear what mitigations we can do.
The text was updated successfully, but these errors were encountered: