dbcve.org
GrafanaApplication

CVE-2022-28660

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The querier component in Grafana Enterprise Logs 1.1.x through 1.3.x before 1.4.0 does not require authentication when X-Scope-OrgID is used. Versions 1.2.1, 1.3.1, and 1.4.0 contain the bugfix. This affects -auth.type=enterprise in microservices mode

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The querier component in Grafana Enterprise Logs versions 1.1.x through 1.3.x contains an authentication bypass vulnerability where requests using the X-Scope-OrgID header are not properly authenticated when the -auth.type=enterprise configuration is used in microservices mode, allowing unauthenticated access to sensitive log data.

MitigationUpgrade to Grafana Enterprise Logs versions 1.2.1, 1.3.1, 1.4.0 or later. Until patched, restrict network access to the querier component using firewall rules or network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 1.1.0, < 1.2.1= 1.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana Enterprise Logs installation
    Locate the Grafana Enterprise Logs binaries or running processes. Common binary names include 'loki' or 'grafana-logs'. Check running processes or installed packages.
    Affected if Grafana Enterprise Logs is present on the system
  2. Determine the installed version
    Run 'loki -version' or check the binary version. Compare the version number against the affected ranges: >= 1.1.0 and < 1.2.1, or exactly 1.3.0
    Affected if Version is 1.1.x, 1.2.0, or 1.3.0
  3. Verify microservices mode is enabled
    Examine the configuration files or command-line arguments for microservices mode operation. Look for '-target=querier' or similar microservice target flags.
    Affected if Loki is running in microservices mode with a separate querier component
  4. Confirm auth.type=enterprise configuration
    Review the configuration files or command-line arguments for '-auth.type=enterprise' or 'auth_type: enterprise'. This setting must be present for the vulnerability to apply.
    Affected if The -auth.type=enterprise configuration option is set
  5. Check querier component network exposure
    Review network configuration, firewall rules, or service bindings to determine if the querier component port is accessible from untrusted networks.
    Affected if The querier component is accessible from networks other than trusted internal networks

The environment is affected if Grafana Enterprise Logs versions 1.1.0 through 1.3.0 are running in microservices mode with -auth.type=enterprise configured and the querier component is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.1 or later
Fixed in 1.2.1
Interim mitigation

Upgrade to Grafana Enterprise Logs versions 1.2.1, 1.3.1, 1.4.0 or later. Until patched, restrict network access to the querier component using firewall rules or network segmentation.

Recommended fix High confidence

Grafana Enterprise Logs 1.4.0

  1. 1. Back up your current Grafana Enterprise Logs configuration and data
  2. 2. Stop the Grafana Enterprise Logs service
  3. 3. Upgrade to version 1.4.0 (or at minimum 1.3.1) of Grafana Enterprise Logs
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Restart the Grafana Enterprise Logs service
  6. 6. Confirm the authentication requirement is now enforced for the querier component in microservices mode with -auth.type=enterprise
Caveat Review release notes for any breaking changes between your current version and 1.4.0, particularly around authentication and microservices behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28660 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data