Skip to content

Lagoon API doesn't always check that a user has permission to view project private key

Moderate
tobybellwood published GHSA-crwh-7mmw-pv2q May 10, 2022

Package

Lagoon API (Lagoon)

Affected versions

<= v2.4.0

Patched versions

v2.4.0

Description

Impact

A user that has access to a project may be able to view a projects private key via some API queries even if they don't have the owner role for that project.

Users that do not have any access to a project are still not able to view project private keys.

Patches

Has the problem been patched? What versions should users upgrade to?

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Severity

Moderate

CVE ID

No known CVE

Weaknesses

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.

Incorrect Permission Assignment for Critical Resource

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. Learn more on MITRE.

Credits