<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
  <DocumentTitle xml:lang="en">Security update for grafana</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE-SU-2025:0545-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-02-14T07:24:15Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-02-14T07:24:15Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-02-14T07:24:15Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf.pl</Engine>
      <Date>2017-02-24T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="Topic" Type="Summary" Ordinal="1" xml:lang="en">Security update for grafana</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This update for grafana fixes the following issues:

grafana was updated from version 9.5.18 to 10.4.13 (jsc#PED-11591,jsc#PED-11649):

- Security issues fixed:
  * CVE-2024-45337: Prevent possible misuse of ServerConfig.PublicKeyCallback by upgrading 
    golang.org/x/crypto (bsc#1234554)
  * CVE-2023-3128: Fixed authentication bypass using Azure AD OAuth (bsc#1212641)
  * CVE-2023-6152: Add email verification when updating user email (bsc#1219912)
  * CVE-2024-6837: Fixed potential data source permission escalation (bsc#1236301)
  * CVE-2024-8118: Fixed permission on external alerting rule write endpoint (bsc#1231024)

- Potential breaking changes in version 10:
  * In panels using the `extract fields` transformation, where one
    of the extracted names collides with one of the already
    existing ields, the extracted field will be renamed.
  * For the existing backend mode users who have table
    visualization might see some inconsistencies on their panels.
    We have updated the table column naming. This will
    potentially affect field transformations and/or field
    overrides. To resolve this either: update transformation or
    field override.
  * For the existing backend mode users who have Transformations
    with the `time` field, might see their transformations are
    not working. Those panels that have broken transformations
    will fail to render. This is because we changed the field
    key. To resolve this either: Remove the affected panel and
    re-create it; Select the `Time` field again; Edit the `time`
    field as `Time` for transformation in `panel.json` or
    `dashboard.json` 
  * The following data source permission endpoints have been removed:
    `GET /datasources/:datasourceId/permissions`
    `POST /api/datasources/:datasourceId/permissions`
    `DELETE /datasources/:datasourceId/permissions`
    `POST /datasources/:datasourceId/enable-permissions`
    `POST /datasources/:datasourceId/disable-permissions`
    + Please use the following endpoints instead:
      `GET /api/access-control/datasources/:uid` for listing data
       source permissions
      `POST /api/access-control/datasources/:uid/users/:id`,
      `POST /api/access-control/datasources/:uid/teams/:id` and
      `POST /api/access-control/datasources/:uid/buildInRoles/:id` 
      for adding or removing data source permissions
  * If you are using Terraform Grafana provider to manage data source permissions, you will need to upgrade your
    provider.
  * For the existing backend mode users who have table visualization might see some inconsistencies on their panels. 
    We have updated the table column naming. This will potentially affect field transformations and/or field overrides.
  * The deprecated `/playlists/{uid}/dashboards` API endpoint has been removed. 
    Dashboard information can be retrieved from the `/dashboard/...` APIs.
  * The `PUT /api/folders/:uid` endpoint no more supports modifying the folder's `UID`
  * Removed all components for the old panel header design.
  * Please review https://grafana.com/docs/grafana/next/breaking-changes/breaking-changes-v10-3/
    for more details
  * OAuth role mapping enforcement: This change impacts GitHub,
    Gitlab, Okta, and Generic OAuth. To avoid overriding manually
    set roles, enable the skip_org_role_sync option in the
    Grafana configuration for your OAuth provider before
    upgrading
  * Angular has been deprecated
  * Grafana legacy alerting has been deprecated
  * API keys are migrating to service accounts
  * The experimental &amp;#8220;dashboard previews&amp;#8221; feature is removed
  * Usernames are now case-insensitive by default
  * Grafana OAuth integrations do not work anymore with email lookups
  * The &amp;#8220;Alias&amp;#8221; field in the CloudWatch data source is removed
  * Athena data source plugin must be updated to version &amp;gt;=2.9.3
  * Redshift data source plugin must be updated to version &amp;gt;=1.8.3
  * DoiT International BigQuery plugin no longer supported
  * Please review https://grafana.com/docs/grafana/next/breaking-changes/breaking-changes-v10-0
    for more details

- This update brings many new features, enhancements and fixes highlighted at:
  * https://grafana.com/docs/grafana/next/whatsnew/whats-new-in-v10-4/
  * https://grafana.com/docs/grafana/next/whatsnew/whats-new-in-v10-3/
  * https://grafana.com/docs/grafana/next/whatsnew/whats-new-in-v10-2/
  * https://grafana.com/docs/grafana/next/whatsnew/whats-new-in-v10-1/
  * https://grafana.com/docs/grafana/next/whatsnew/whats-new-in-v10-0/
</Note>
    <Note Title="Terms of Use" Type="Legal Disclaimer" Ordinal="3" xml:lang="en">The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).</Note>
    <Note Title="Patchnames" Type="Details" Ordinal="4" xml:lang="en">SUSE-2025-545,SUSE-SLE-Module-Packagehub-Subpackages-15-SP6-2025-545,openSUSE-SLE-15.6-2025-545</Note>
  </DocumentNotes>
  <DocumentDistribution xml:lang="en">Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0)</DocumentDistribution>
  <DocumentReferences>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      <Description>Link for SUSE-SU-2025:0545-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2025-February/020341.html</URL>
      <Description>E-Mail link for SUSE-SU-2025:0545-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1212641</URL>
      <Description>SUSE Bug 1212641</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1219912</URL>
      <Description>SUSE Bug 1219912</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1231024</URL>
      <Description>SUSE Bug 1231024</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1234554</URL>
      <Description>SUSE Bug 1234554</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1236301</URL>
      <Description>SUSE Bug 1236301</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2023-3128/</URL>
      <Description>SUSE CVE CVE-2023-3128 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2023-6152/</URL>
      <Description>SUSE CVE CVE-2023-6152 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-45337/</URL>
      <Description>SUSE CVE CVE-2024-45337 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-6837/</URL>
      <Description>SUSE CVE CVE-2024-6837 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-8118/</URL>
      <Description>SUSE CVE CVE-2024-8118 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Module for Package Hub 15 SP6">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Module for Package Hub 15 SP6">
        <FullProductName ProductID="SUSE Linux Enterprise Module for Package Hub 15 SP6" CPE="cpe:/o:suse:packagehub:15:sp6">SUSE Linux Enterprise Module for Package Hub 15 SP6</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="openSUSE Leap 15.6">
      <Branch Type="Product Name" Name="openSUSE Leap 15.6">
        <FullProductName ProductID="openSUSE Leap 15.6" CPE="cpe:/o:opensuse:leap:15.6">openSUSE Leap 15.6</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="grafana-10.4.13-150200.3.59.1">
      <FullProductName ProductID="grafana-10.4.13-150200.3.59.1">grafana-10.4.13-150200.3.59.1</FullProductName>
    </Branch>
    <Relationship ProductReference="grafana-10.4.13-150200.3.59.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Module for Package Hub 15 SP6">
      <FullProductName ProductID="SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1">grafana-10.4.13-150200.3.59.1 as a component of SUSE Linux Enterprise Module for Package Hub 15 SP6</FullProductName>
    </Relationship>
    <Relationship ProductReference="grafana-10.4.13-150200.3.59.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Leap 15.6">
      <FullProductName ProductID="openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1">grafana-10.4.13-150200.3.59.1 as a component of openSUSE Leap 15.6</FullProductName>
    </Relationship>
  </ProductTree>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="1">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Grafana is validating Azure AD accounts based on the email claim. 

On Azure AD, the profile email field is not unique and can be easily modified. 

This leads to account takeover and authentication bypass when Azure AD OAuth is configured with a multi-tenant app. 

</Note>
    </Notes>
    <CVE>CVE-2023-3128</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1</ProductID>
        <ProductID>openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>critical</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2023-3128.html</URL>
        <Description>CVE-2023-3128</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1212641</URL>
        <Description>SUSE Bug 1212641</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="2">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">A user changing their email after signing up and verifying it can change it without verification in profile settings.

The configuration option "verify_email_enabled" will only validate email only on sign up.

</Note>
    </Notes>
    <CVE>CVE-2023-6152</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1</ProductID>
        <ProductID>openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2023-6152.html</URL>
        <Description>CVE-2023-6152</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1219912</URL>
        <Description>SUSE Bug 1219912</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="3">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.</Note>
    </Notes>
    <CVE>CVE-2024-45337</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1</ProductID>
        <ProductID>openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-45337.html</URL>
        <Description>CVE-2024-45337</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1234482</URL>
        <Description>SUSE Bug 1234482</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="4">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.</Note>
    </Notes>
    <CVE>CVE-2024-6837</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1</ProductID>
        <ProductID>openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-6837.html</URL>
        <Description>CVE-2024-6837</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1236301</URL>
        <Description>SUSE Bug 1236301</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="5">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Grafana, the wrong permission is applied to the alert rule write API endpoint, allowing users with permission to write external alert instances to also write alert rules.</Note>
    </Notes>
    <CVE>CVE-2024-8118</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Enterprise Module for Package Hub 15 SP6:grafana-10.4.13-150200.3.59.1</ProductID>
        <ProductID>openSUSE Leap 15.6:grafana-10.4.13-150200.3.59.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL>https://www.suse.com/support/update/announcement/2025/suse-su-20250545-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-8118.html</URL>
        <Description>CVE-2024-8118</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1231024</URL>
        <Description>SUSE Bug 1231024</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
