ghsa-rf3g-v8p5-p675
Vulnerability from github
Published
2022-12-05 23:06
Modified
2022-12-05 23:06
Severity ?
9.4 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Summary
NodeBB vulnerable to account takeover via prototype vulnerability
Details

Impact

Due to a plain object with a prototype being used in socket.io message handling a specially crafted payload can be used to impersonate other users and takeover accounts.

Patches

Patched in 2.6.1

Workarounds

Site maintainers can cherry-pick https://github.com/NodeBB/NodeBB/commit/48d143921753914da45926cca6370a92ed0c46b8 into their codebase to patch the exploit.

For more information

If you have any questions or comments about this advisory:

Discuss it on our community forum Email us at support@nodebb.org

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "npm",
            name: "nodebb",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.6.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-46164",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-665",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-12-05T23:06:14Z",
      nvd_published_at: "2022-12-05T21:15:00Z",
      severity: "CRITICAL",
   },
   details: "### Impact\nDue to a plain object with a prototype being used in socket.io message handling a specially crafted payload can be used to impersonate other users and takeover accounts.\n\n### Patches\nPatched in 2.6.1\n\n### Workarounds\nSite maintainers can cherry-pick https://github.com/NodeBB/NodeBB/commit/48d143921753914da45926cca6370a92ed0c46b8 into their codebase to patch the exploit.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\nDiscuss it on [our community forum](https://github.com/NodeBB/NodeBB/security/advisories/community.nodebb.org/)\nEmail us at [support@nodebb.org](mailto:support@nodebb.org)\n",
   id: "GHSA-rf3g-v8p5-p675",
   modified: "2022-12-05T23:06:14Z",
   published: "2022-12-05T23:06:14Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/NodeBB/NodeBB/security/advisories/GHSA-rf3g-v8p5-p675",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-46164",
      },
      {
         type: "WEB",
         url: "https://github.com/NodeBB/NodeBB/commit/48d143921753914da45926cca6370a92ed0c46b8",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/NodeBB/NodeBB",
      },
      {
         type: "WEB",
         url: "https://github.com/NodeBB/NodeBB/releases/tag/v2.6.1",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
         type: "CVSS_V3",
      },
   ],
   summary: "NodeBB vulnerable to account takeover via prototype vulnerability",
}


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.