Skip to content

GHSA-66c4-2g2v-54qw BIT-grafana-2024-10452 CVE-2024-10452 GO-2024-3240

Grafana org admin can delete pending invites in different org

Low Go
Severity
0.0 / 10
Low · CVSS 4.0
Exploit chance (EPSS)
0.49%
Chance of exploitation in the next 30 days. Higher than 42.14% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Fix
None yet
No fixed version published

Description

Organization admins can delete pending invites created in an organization they are not part of.

Affected versions

Go

PackageVulnerableFixed in
github.com/grafana/grafana
<= 10.4.0
No fix yet
github.com/grafana/grafana
all versions
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
High
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 2.2

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

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

Weakness

CWE-639: Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How to prevent it
  • Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
  • Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
  • Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-8pjx-jj86-j47p
Grafana path traversal
High Known exploited Also affects github.com/grafana/grafana
CVE-2021-39226
Authentication bypass for viewing and deletions of snapshots
High Known exploited Also affects github.com/grafana/grafana
GHSA-3w66-95m3-8jxg
Grafana: Pre-authentication denial of service in the public dashboard query handler
High Also affects github.com/grafana/grafana
GHSA-9g84-39mm-q4p3
Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug
Medium Also affects github.com/grafana/grafana
GHSA-f74p-cwhp-x2wx
Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability.
High Also affects github.com/grafana/grafana
GHSA-9493-h4f5-633x
Grafana: Path traversal in the Tempo and Loki data source plugins
Medium Also affects github.com/grafana/grafana
GHSA-wfhv-mj62-f5xh
Grafana: Users can generate Service Account tokens after permissions removal
High Also affects github.com/grafana/grafana
GHSA-gxcp-jjxh-rwp4
Grafana: SQL Expressions Read File From Disk
Medium Also affects github.com/grafana/grafana
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor