Bug: InQuest hash error message uses undefined variable
Hey maintainers.... I was going through the codebase and noticed a small bug in the inquest.py.
What's happening:
In api_app/analyzers_manager/observable_analyzers/inquest.py, the InQuest.hash_type property is supposed to raise an AnalyzerRunException with a helpful message when a HASH observable has an unsupported length.
Instead, the exception message references an undefined variable (hash) in the f-string, which triggers a NameError and crashes the analyzer before it can return a proper IntelOwl error.
Why this matters:
- Users get a confusing internal error (
NameError) instead of a clear “unsupported hash type” message.
- Breaks analysis runs for invalid inputs and makes debugging harder.
Bug: InQuest hash error message uses undefined variable
Hey maintainers.... I was going through the codebase and noticed a small bug in the
inquest.py.What's happening:
In
api_app/analyzers_manager/observable_analyzers/inquest.py, theInQuest.hash_typeproperty is supposed to raise anAnalyzerRunExceptionwith a helpful message when a HASH observable has an unsupported length.Instead, the exception message references an undefined variable (
hash) in the f-string, which triggers aNameErrorand crashes the analyzer before it can return a proper IntelOwl error.Why this matters:
NameError) instead of a clear “unsupported hash type” message.