Skip to content

DefectDojo Security Advisory: Severity Medium | Potential GitHub Authentication Misconfiguration

Moderate
devGregA published GHSA-hfp4-q5pg-2p7r Feb 27, 2023

Package

DefectDojo

Affected versions

< 2.19.4

Patched versions

2.19.4

Description

Details:

The DefectDojo documentation referenced an SSO implementation for GitHub that used service level authentication rather than ‘org’ or ‘team’ level authentication.

Impact:

For instances with GitHub OAuth2 enabled, that followed the DefectDojo documentation, any user with a GitHub account could authenticate, however it is important to note that a user would be limited to viewing test types and environment types (permission of least privilege in DefectDojo).

Mitigation:

We are aware that this functionality is a valid use case for MSP’s using DefectDojo. However to help protect any organizations who may have misconfigured, we’ve issued an update (2.19.4) that will cause a breaking change for instances with GitHub OAuth2 enabled, per the DefectDojo documentation. No SaaS customers are impacted by either the issue or the breaking change. For people who desire service level authentication, both DefectDojo’s context processor and settings must be updated.

Credit:

We greatly appreciate Ben Smith & Tim Birkett of PortSwigger for reporting this issue.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits