mandiant / mandiant/capa-rules
interact with driver via control codes
Open
Nobody has claimed this yet.
false positive
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
## Summary
`DeviceIoControl` does not necessarily communicate to a driver. The device can also be a volume, directory, file, or stream.
Probably a good idea to tighten it up here or remove the API all together.
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 by locating the capa rule or API entry point that handles DeviceIoControl and review how its control codes are represented. Determine whether the intended outcome is to tighten the rule or remove the API, including the volume, directory, file, and stream cases named in the issue. Done requires an agreed scope and corresponding rule or API changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100