| 标题 | OWASP DefectDojo < 2.56.0 Authorization Bypass |
|---|
| 描述 | DefectDojo does not properly validate that the supplied risk_acceptance ID (raid) belongs to the supplied engagement ID (eid).
Authorization decorator checks only the engagement (@user_is_authorized on eid), while functions view_edit_risk_acceptance, edit_risk_acceptance, expire_risk_acceptance, reinstate_risk_acceptance and delete_risk_acceptance simply do get_object_or_404(Risk_Acceptance, pk=raid) without any affiliation check.
Only the download_risk_acceptance endpoint contains the correct check:
if not Engagement.objects.filter(risk_acceptance=risk_acceptance, id=eid).exists(): raise PermissionDenied
As a result, any authenticated user who has access to at least one engagement can read, edit, expire, reinstate or delete Risk Acceptance objects (and all accepted findings inside them) that belong to any other product/engagement. |
|---|
| 来源 | ⚠️ https://github.com/noname1337h1/cve-bug-bounty/blob/main/dfdj_risk_acceptance_raid_idor_authorization_bypass/dfdj_risk_acceptance_raid_idor_authorization_bypass.md |
|---|
| 用户 | noname1337 (UID 97313) |
|---|
| 提交 | 2026-04-13 20時19分 (6 月前) |
|---|
| 管理 | 2026-04-30 17時17分 (17 days later) |
|---|
| 状态 | 已接受 |
|---|
| VulDB条目 | 360317 [OWASP DefectDojo 直到 2.55.4 Benchmark/Engagement/Product/Survey 权限提升] |
|---|
| 积分 | 20 |
|---|