mandiant / mandiant/capa-rules
bytes feature unable to detect CLSID/RID when pushed via stack
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
## Summary
The following example of a code in Examples currently does not match the relevant rule `schedule-task-via-itaskservice`, even when the rule was stripped down to just the `bytes` features, suggesting the bytes feature is currently unable to detect such bytes when pushed via stack at the moment.
## Examples
## Possible improvements
## Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the `schedule-task-via-itaskservice` rule and the code sample shown in the issue’s Examples section; reproduce the false negative with the rule reduced to its `bytes` features. Trace how the bytes feature handles values pushed via stack. Done means the supplied example matches the relevant rule; the issue names no file or test to use.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100