CVE-2022-39229 (GCVE-0-2022-39229)
Vulnerability from cvelistv5
Published
2022-10-13 00:00
Modified
2024-08-03 12:00
Severity ?
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Summary
Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana user’s username and email address are unique fields, that means no other user can have the same username or email address as another user. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`’s email address. This prevents `user_1` logging into the application since `user_1`'s password won’t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue.
References
security-advisories@github.comhttps://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35Patch, Third Party Advisory
security-advisories@github.comhttps://github.com/grafana/grafana/releases/tag/v9.1.8Third Party Advisory
security-advisories@github.comhttps://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289rThird Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35Patch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/grafana/grafana/releases/tag/v9.1.8Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289rThird Party Advisory
Impacted products
Vendor Product Version
grafana grafana Version: >= 9.0.0, < 9.1.8
Version: >= 8.5.0, < 8.5.14
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T12:00:43.379Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/grafana/grafana/releases/tag/v9.1.8",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "grafana",
               vendor: "grafana",
               versions: [
                  {
                     status: "affected",
                     version: ">= 9.0.0, < 9.1.8",
                  },
                  {
                     status: "affected",
                     version: ">= 8.5.0, < 8.5.14",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana user’s username and email address are unique fields, that means no other user can have the same username or email address as another user. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`’s email address. This prevents `user_1` logging into the application since `user_1`'s password won’t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "LOW",
                  baseScore: 4.3,
                  baseSeverity: "MEDIUM",
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  privilegesRequired: "LOW",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-287",
                     description: "CWE-287: Improper Authentication",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-10-13T00:00:00",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               url: "https://github.com/grafana/grafana/releases/tag/v9.1.8",
            },
            {
               url: "https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r",
            },
            {
               url: "https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35",
            },
         ],
         source: {
            advisory: "GHSA-gj7m-853r-289r",
            discovery: "UNKNOWN",
         },
         title: "Grafana users with email as a username can block other users from signing in",
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2022-39229",
      datePublished: "2022-10-13T00:00:00",
      dateReserved: "2022-09-02T00:00:00",
      dateUpdated: "2024-08-03T12:00:43.379Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         configurations: "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"8.5.14\", \"matchCriteriaId\": \"3959EA7C-8C8F-4CA2-B33F-F9BBAB8CD15C\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"9.0.0\", \"versionEndExcluding\": \"9.1.8\", \"matchCriteriaId\": \"E8E1ACC7-F43B-4395-A1FD-44CAEB43430D\"}]}]}]",
         descriptions: "[{\"lang\": \"en\", \"value\": \"Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana user\\u2019s username and email address are unique fields, that means no other user can have the same username or email address as another user. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`\\u2019s email address. This prevents `user_1` logging into the application since `user_1`'s password won\\u2019t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue.\"}, {\"lang\": \"es\", \"value\": \"Grafana es una plataforma de visualizaci\\u00f3n de datos de c\\u00f3digo abierto para m\\u00e9tricas, registros y trazas. Las versiones anteriores a 9.1.8 y 8.5.14 permiten que un usuario bloquee el intento de inicio de sesi\\u00f3n de otro al registrar la direcci\\u00f3n de correo electr\\u00f3nico de otra persona como nombre de usuario. El nombre de usuario y la direcci\\u00f3n de correo electr\\u00f3nico de un usuario de Grafana son campos \\u00fanicos, lo que significa que ning\\u00fan otro usuario puede tener el mismo nombre de usuario o direcci\\u00f3n de correo electr\\u00f3nico que otro usuario. Un usuario puede tener una direcci\\u00f3n de correo electr\\u00f3nico como nombre de usuario. Sin embargo, el sistema de inicio de sesi\\u00f3n permite a usuarios conectarse con cualquier nombre de usuario o direcci\\u00f3n de correo electr\\u00f3nico. Dado que Grafana permite que un usuario sea registrado con su nombre de usuario o con su direcci\\u00f3n de correo electr\\u00f3nico, esto crea un comportamiento habitual en el que \\\"user_1\\\" puede registrarse con una direcci\\u00f3n de correo electr\\u00f3nico y \\\"user_2\\\" puede registrar su nombre de usuario como la direcci\\u00f3n de correo electr\\u00f3nico de \\\"user_1\\\". Esto impide que \\\"user_1\\\" sea registrado en la aplicaci\\u00f3n, ya que la contrase\\u00f1a de \\\"user_1\\\" no coincide con la direcci\\u00f3n de correo electr\\u00f3nico de \\\"user_2\\\". Las versiones 9.1.8 y 8.5.14 contienen un parche. No se presentan mitigaciones para este problema\"}]",
         id: "CVE-2022-39229",
         lastModified: "2024-11-21T07:17:50.027",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L\", \"baseScore\": 4.3, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"LOW\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 1.4}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L\", \"baseScore\": 4.3, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"LOW\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 1.4}]}",
         published: "2022-10-13T23:15:10.937",
         references: "[{\"url\": \"https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/grafana/grafana/releases/tag/v9.1.8\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/grafana/grafana/releases/tag/v9.1.8\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Third Party Advisory\"]}]",
         sourceIdentifier: "security-advisories@github.com",
         vulnStatus: "Modified",
         weaknesses: "[{\"source\": \"security-advisories@github.com\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-287\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2022-39229\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2022-10-13T23:15:10.937\",\"lastModified\":\"2024-11-21T07:17:50.027\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Grafana is an open source data visualization platform for metrics, logs, and traces. Versions prior to 9.1.8 and 8.5.14 allow one user to block another user's login attempt by registering someone else'e email address as a username. A Grafana user’s username and email address are unique fields, that means no other user can have the same username or email address as another user. A user can have an email address as a username. However, the login system allows users to log in with either username or email address. Since Grafana allows a user to log in with either their username or email address, this creates an usual behavior where `user_1` can register with one email address and `user_2` can register their username as `user_1`’s email address. This prevents `user_1` logging into the application since `user_1`'s password won’t match with `user_2`'s email address. Versions 9.1.8 and 8.5.14 contain a patch. There are no workarounds for this issue.\"},{\"lang\":\"es\",\"value\":\"Grafana es una plataforma de visualización de datos de código abierto para métricas, registros y trazas. Las versiones anteriores a 9.1.8 y 8.5.14 permiten que un usuario bloquee el intento de inicio de sesión de otro al registrar la dirección de correo electrónico de otra persona como nombre de usuario. El nombre de usuario y la dirección de correo electrónico de un usuario de Grafana son campos únicos, lo que significa que ningún otro usuario puede tener el mismo nombre de usuario o dirección de correo electrónico que otro usuario. Un usuario puede tener una dirección de correo electrónico como nombre de usuario. Sin embargo, el sistema de inicio de sesión permite a usuarios conectarse con cualquier nombre de usuario o dirección de correo electrónico. Dado que Grafana permite que un usuario sea registrado con su nombre de usuario o con su dirección de correo electrónico, esto crea un comportamiento habitual en el que \\\"user_1\\\" puede registrarse con una dirección de correo electrónico y \\\"user_2\\\" puede registrar su nombre de usuario como la dirección de correo electrónico de \\\"user_1\\\". Esto impide que \\\"user_1\\\" sea registrado en la aplicación, ya que la contraseña de \\\"user_1\\\" no coincide con la dirección de correo electrónico de \\\"user_2\\\". Las versiones 9.1.8 y 8.5.14 contienen un parche. No se presentan mitigaciones para este problema\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L\",\"baseScore\":4.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.8,\"impactScore\":1.4},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L\",\"baseScore\":4.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.8,\"impactScore\":1.4}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-287\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"8.5.14\",\"matchCriteriaId\":\"3959EA7C-8C8F-4CA2-B33F-F9BBAB8CD15C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:grafana:grafana:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"9.0.0\",\"versionEndExcluding\":\"9.1.8\",\"matchCriteriaId\":\"E8E1ACC7-F43B-4395-A1FD-44CAEB43430D\"}]}]}],\"references\":[{\"url\":\"https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/grafana/grafana/releases/tag/v9.1.8\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/grafana/grafana/commit/5644758f0c5ae9955a4e5480d71f9bef57fdce35\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/grafana/grafana/releases/tag/v9.1.8\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/grafana/grafana/security/advisories/GHSA-gj7m-853r-289r\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.