Vulnerability-Lookup

CVE-2024-38351 (GCVE-0-2024-38351)

Vulnerability from cvelistv5 – Published: 2024-06-18 17:00 – Updated: 2024-08-02 04:04

Title

Password auth and OAuth2 unverified email linking

Summary

Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user's email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user's email and associate them, 4. because we haven't changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn't verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for "unrecognized device" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.

Severity

5.4 (Medium)


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

CWE

CWE-287 - Improper Authentication

Assigner

GitHub_M

References

2 references

URL	Tags
https://github.com/pocketbase/pocketbase/security…	x_refsource_CONFIRM
https://github.com/pocketbase/pocketbase/discussi…	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
pocketbase	pocketbase	Affected: < 0.22.14

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-38351",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-07-11T17:12:37.426670Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-07-12T15:53:03.984Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T04:04:25.276Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v",
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v"
          },
          {
            "name": "https://github.com/pocketbase/pocketbase/discussions/4355",
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/pocketbase/pocketbase/discussions/4355"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "pocketbase",
          "vendor": "pocketbase",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.22.14"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user\u0027s email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user\u0027s email and associate them, 4. because we haven\u0027t changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn\u0027t verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for \"unrecognized device\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.\n\n"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.4,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287: Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-06-18T17:00:38.595Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v"
        },
        {
          "name": "https://github.com/pocketbase/pocketbase/discussions/4355",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/pocketbase/pocketbase/discussions/4355"
        }
      ],
      "source": {
        "advisory": "GHSA-m93w-4fxv-r35v",
        "discovery": "UNKNOWN"
      },
      "title": "Password auth and OAuth2 unverified email linking"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2024-38351",
    "datePublished": "2024-06-18T17:00:38.595Z",
    "dateReserved": "2024-06-14T14:16:16.463Z",
    "dateUpdated": "2024-08-02T04:04:25.276Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-38351",
      "date": "2026-05-25",
      "epss": "0.00188",
      "percentile": "0.40223"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-38351\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-06-18T17:15:52.777\",\"lastModified\":\"2024-11-21T09:25:25.250\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user\u0027s email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user\u0027s email and associate them, 4. because we haven\u0027t changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn\u0027t verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for \\\"unrecognized device\\\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.\\n\\n\"},{\"lang\":\"es\",\"value\":\"Pocketbase es un backend web de c\u00f3digo abierto escrito en go. En las versiones afectadas, un usuario malintencionado puede comprometer las cuentas de otros usuarios. Para ser explotados, los usuarios deben tener habilitados los m\u00e9todos de autenticaci\u00f3n OAuth2 y Contrase\u00f1a. Un posible escenario de ataque podr\u00eda ser: 1. un actor malintencionado se registra con el correo electr\u00f3nico del usuario objetivo (no est\u00e1 verificado), 2. en alg\u00fan momento posterior, el usuario objetivo tropieza con su aplicaci\u00f3n y decide registrarse con OAuth2 (_este paso El atacante tambi\u00e9n podr\u00eda iniciarlo enviando un correo electr\u00f3nico de invitaci\u00f3n al usuario objetivo_), 3. en una autenticaci\u00f3n OAuth2 exitosa, buscamos un usuario de PocketBase existente que coincida con el correo electr\u00f3nico del usuario OAuth2 y lo asociamos, 4. porque no hemos cambiado el contrase\u00f1a del usuario de PocketBase existente durante la vinculaci\u00f3n, el actor malicioso tiene acceso a la cuenta de usuario objetivo y podr\u00e1 iniciar sesi\u00f3n con el correo electr\u00f3nico/contrase\u00f1a creado inicialmente. Para evitar que esto suceda, ahora restablecemos la contrase\u00f1a para este caso espec\u00edfico si el usuario creado anteriormente no fue verificado (una excepci\u00f3n a esto es si el enlace es expl\u00edcito/manual, tambi\u00e9n conocido como cuando env\u00eda `Autorizaci\u00f3n:TOKEN` con OAuth2 llamada de autenticaci\u00f3n). Adem\u00e1s, para advertir a los usuarios existentes, ahora enviamos una alerta por correo electr\u00f3nico en caso de que el usuario haya iniciado sesi\u00f3n con contrase\u00f1a pero tenga al menos una cuenta OAuth2 vinculada. El flujo se mejorar\u00e1 a\u00fan m\u00e1s con la refactorizaci\u00f3n continua y comenzaremos a enviar correos electr\u00f3nicos para inicios de sesi\u00f3n de \\\"dispositivos no reconocidos\\\" (OTP y MFA ya est\u00e1n implementados y estar\u00e1n disponibles con la pr\u00f3xima versi\u00f3n v0.23.0 en un futuro pr\u00f3ximo). Por el momento, se recomienda a los usuarios que actualicen a la versi\u00f3n 0.22.14. No se conocen workarounds para esta vulnerabilidad.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N\",\"baseScore\":5.4,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"REQUIRED\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":2.5}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-287\"}]}],\"references\":[{\"url\":\"https://github.com/pocketbase/pocketbase/discussions/4355\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/pocketbase/pocketbase/discussions/4355\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-38351\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-07-11T17:12:37.426670Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-07-11T17:12:43.053Z\"}}], \"cna\": {\"title\": \"Password auth and OAuth2 unverified email linking\", \"source\": {\"advisory\": \"GHSA-m93w-4fxv-r35v\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.4, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"REQUIRED\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}}], \"affected\": [{\"vendor\": \"pocketbase\", \"product\": \"pocketbase\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 0.22.14\"}]}], \"references\": [{\"url\": \"https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v\", \"name\": \"https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/pocketbase/pocketbase/discussions/4355\", \"name\": \"https://github.com/pocketbase/pocketbase/discussions/4355\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user\u0027s email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user\u0027s email and associate them, 4. because we haven\u0027t changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn\u0027t verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for \\\"unrecognized device\\\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.\\n\\n\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-287\", \"description\": \"CWE-287: Improper Authentication\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2024-06-18T17:00:38.595Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-38351\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-07-12T15:53:03.984Z\", \"dateReserved\": \"2024-06-14T14:16:16.463Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2024-06-18T17:00:38.595Z\", \"assignerShortName\": \"GitHub_M\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}

FKIE_CVE-2024-38351

Vulnerability from fkie_nvd - Published: 2024-06-18 17:15 - Updated: 2026-04-15 00:35

Severity

5.4 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Summary

References

	URL	Tags
	security-advisories@github.com	https://github.com/pocketbase/pocketbase/discussions/4355
	security-advisories@github.com	https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v
	af854a3a-2127-422b-91ae-364da2661108	https://github.com/pocketbase/pocketbase/discussions/4355
	af854a3a-2127-422b-91ae-364da2661108	https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user\u0027s email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user\u0027s email and associate them, 4. because we haven\u0027t changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn\u0027t verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for \"unrecognized device\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.\n\n"
    },
    {
      "lang": "es",
      "value": "Pocketbase es un backend web de c\u00f3digo abierto escrito en go. En las versiones afectadas, un usuario malintencionado puede comprometer las cuentas de otros usuarios. Para ser explotados, los usuarios deben tener habilitados los m\u00e9todos de autenticaci\u00f3n OAuth2 y Contrase\u00f1a. Un posible escenario de ataque podr\u00eda ser: 1. un actor malintencionado se registra con el correo electr\u00f3nico del usuario objetivo (no est\u00e1 verificado), 2. en alg\u00fan momento posterior, el usuario objetivo tropieza con su aplicaci\u00f3n y decide registrarse con OAuth2 (_este paso El atacante tambi\u00e9n podr\u00eda iniciarlo enviando un correo electr\u00f3nico de invitaci\u00f3n al usuario objetivo_), 3. en una autenticaci\u00f3n OAuth2 exitosa, buscamos un usuario de PocketBase existente que coincida con el correo electr\u00f3nico del usuario OAuth2 y lo asociamos, 4. porque no hemos cambiado el contrase\u00f1a del usuario de PocketBase existente durante la vinculaci\u00f3n, el actor malicioso tiene acceso a la cuenta de usuario objetivo y podr\u00e1 iniciar sesi\u00f3n con el correo electr\u00f3nico/contrase\u00f1a creado inicialmente. Para evitar que esto suceda, ahora restablecemos la contrase\u00f1a para este caso espec\u00edfico si el usuario creado anteriormente no fue verificado (una excepci\u00f3n a esto es si el enlace es expl\u00edcito/manual, tambi\u00e9n conocido como cuando env\u00eda `Autorizaci\u00f3n:TOKEN` con OAuth2 llamada de autenticaci\u00f3n). Adem\u00e1s, para advertir a los usuarios existentes, ahora enviamos una alerta por correo electr\u00f3nico en caso de que el usuario haya iniciado sesi\u00f3n con contrase\u00f1a pero tenga al menos una cuenta OAuth2 vinculada. El flujo se mejorar\u00e1 a\u00fan m\u00e1s con la refactorizaci\u00f3n continua y comenzaremos a enviar correos electr\u00f3nicos para inicios de sesi\u00f3n de \"dispositivos no reconocidos\" (OTP y MFA ya est\u00e1n implementados y estar\u00e1n disponibles con la pr\u00f3xima versi\u00f3n v0.23.0 en un futuro pr\u00f3ximo). Por el momento, se recomienda a los usuarios que actualicen a la versi\u00f3n 0.22.14. No se conocen workarounds para esta vulnerabilidad."
    }
  ],
  "id": "CVE-2024-38351",
  "lastModified": "2026-04-15T00:35:42.020",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.4,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 2.5,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2024-06-18T17:15:52.777",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/pocketbase/pocketbase/discussions/4355"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://github.com/pocketbase/pocketbase/discussions/4355"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-287"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}

GHSA-M93W-4FXV-R35V

Vulnerability from github – Published: 2024-06-18 20:29 – Updated: 2024-07-05 21:42

Summary

PocketBase performs password auth and OAuth2 unverified email linking

Details

In order to be exploited you must have both OAuth2 and Password auth methods enabled.

A possible attack scenario could be: - a malicious actor register with the targeted user's email (it is unverified) - at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (this step could be also initiated by the attacker by sending an invite email to the targeted user) - on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user's email and associate them - because we haven't changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password

To prevent this for happening we now reset the password for this specific case if the previously created user wasn't verified (an exception to this is if the linking is explicit/manual, aka. when you send Authorization:TOKEN with the OAuth2 auth call).

Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. It looks something like:

Hello, Just to let you know that someone has logged in to your Acme account using a password while you already have OAuth2 GitLab auth linked. If you have recently signed in with a password, you may disregard this email. If you don't recognize the above action, you should immediately change your Acme account password. Thanks, Acme team

The flow will be further improved with the ongoing refactoring and we will start sending emails for "unrecognized device" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future).

Severity

5.4 (Medium)


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

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pocketbase/pocketbase"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.22.14"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-38351"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-06-18T20:29:33Z",
    "nvd_published_at": "2024-06-18T17:15:52Z",
    "severity": "MODERATE"
  },
  "details": "**In order to be exploited you must have both OAuth2 and Password auth methods enabled.**\n\nA possible attack scenario could be:\n- a malicious actor register with the targeted user\u0027s email (it is unverified)\n- at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_) \n- on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user\u0027s email and associate them\n- because we haven\u0027t changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password\n\nTo prevent this for happening we now reset the password for this specific case if the previously created user wasn\u0027t verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call).\n\nAdditionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. It looks something like:\n\n_Hello,\nJust to let you know that someone has logged in to your Acme account using a password while you already have OAuth2 GitLab auth linked.\nIf you have recently signed in with a password, you may disregard this email.\n**If you don\u0027t recognize the above action, you should immediately change your Acme account password.**\nThanks,\nAcme team_\n\nThe flow will be further improved with the [ongoing refactoring](https://github.com/pocketbase/pocketbase/discussions/4355) and we will start sending emails for \"unrecognized device\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future).\n\n",
  "id": "GHSA-m93w-4fxv-r35v",
  "modified": "2024-07-05T21:42:20Z",
  "published": "2024-06-18T20:29:33Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38351"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pocketbase/pocketbase/commit/58ace5d5e7b9b979490019cf8d1b88491e5daec5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pocketbase/pocketbase"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pocketbase/pocketbase/discussions/4355"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "PocketBase performs password auth and OAuth2 unverified email linking"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2024-38351 (GCVE-0-2024-38351)

FKIE_CVE-2024-38351

GHSA-M93W-4FXV-R35V

Tags

Sightings

Nomenclature