Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
paratestphp/paratest
7.x @ 30dedd9
2
Fixes
0
CVEs
MEDIUM
Peak severity
Highlights
Privilege Escalation: 2 prior fixes. Scrutinize any change in this area.
(.github/workflows/stale.yml): most-fixed (1 issue). Treat as high-risk during review.
0 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Privilege Escalation: Overly broad default GITHUB_TOKEN permissions in the primary continuous integration (CI) workflow can allow compromised dependencies or malicious pull requests to escalate privileges within the repository context. Explicitly declaring read-only permissions prevents this attack vector.
Privilege Escalation: Automated administrative workflows like stale branch cleanup could run with elevated token write privileges, making them targets for exploit if a runner or workflow step is compromised.