DO01 - wrong condition check?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Description
"DO01": {
"description": "Potential Excessive Resource Consumption",
"source": Element,
"target": (Process, Server),
"condition": "target.handlesResourceConsumption is False",
Without knowing when handlesResourceConsumption should be set to True, the check here appears to not do what is intended. Excessive resource consumption is subjective, and would be a result of memory or resource leaks, and even managed code (e.g. JVM or .NET based Processes) can still run out of file descriptors. There is not enough information in the dataflows to know if resource consumption will be excessive, imho. It should be possible to know if resource consumption could be an issue if e.g. the Process is multi-tenant/multi-user e.g. a RESTful web server or a database.
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 tracing the DO01 threat definition and every reference to handlesResourceConsumption in the repository. Determine and document the intended condition for excessive resource consumption, then confirm the agreed behavior with maintainers; done means the rule's semantics are explicit and its condition is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100