How "model.Rates" works ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by tracing model.Rates and the vulnerability exploitation entry point to determine whether successRate is consulted during exploitation. Document the observed behavior and clarify whether a rate of 0.0 should prevent successful exploitation.
Written by the indexing model from the issue text.
Description
I am wondering how "model.Rates" works.
For example :
vulname = m.VulnerabilityInfo(
...
rates=m.Rates(successRate=1.0)
),
I couldn't find where the variable "successRate" is used to calculate whether an exploitation succeeds or not.
( I means : When I tried to define successRates as 0.0 , the vulneraility still exploits successfully. )
- Dominant language
- Jupyter Notebook
- Stars
- 1.8k
- Forks
- 286
- Avg merge
- 4h 35m
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/CyberBattleSim
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/CyberBattleSim#156 ·
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/CyberBattleSim#117 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/CyberBattleSim#115 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/CyberBattleSim#96 · 3 comments ·
-
needsclarification question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/CyberBattleSim#90 · 1 comment ·
All issues in microsoft/CyberBattleSim
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AXERA-TECH/ax-llm#75 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100