ghsa-9qpj-qq2r-5mcc
Vulnerability from github
Published
2023-05-26 13:52
Modified
2023-05-26 13:52
Summary
html inputs of type password recorded in plaintext when converted to text inputs
Details

Impact

Highlight may record passwords on customer deployments when a password html input is switched to type="text" via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates type="password" inputs. A customer may assume that switching to type="text" would also not record this input; hence, they would not add additional highlight-mask css-class obfuscation to this part of the DOM, resulting in unintentional recording of a password value when a Show Password button is used.

Patches

highlight.run@6.0.0 resolves the issue via https://github.com/rrweb-io/rrweb/pull/1184 This patch tracks changes to the type attribute of an input to ensure an input that used to be a type="password" continues to be obfuscated.

Workarounds

We have deployed a change to our data ingest to obfuscate passwords server side from older clients. This means that upgrading to the latest version of highlight.run is not necessary but recommended to prevent potential network transfer of recorded password data to our backend.

References

https://github.com/rrweb-io/rrweb/pull/1184

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "highlight.run"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-33187"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-319"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-05-26T13:52:19Z",
    "nvd_published_at": "2023-05-26T21:15:20Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nHighlight may record passwords on customer deployments when a password html input is switched to `type=\"text\"` via a javascript \"Show Password\" button. This differs from the expected behavior which always obfuscates `type=\"password\"` inputs. A customer may assume that switching to `type=\"text\"` would also not record this input; hence, they would not add additional `highlight-mask` css-class obfuscation to this part of the DOM, resulting in unintentional recording of a password value when a `Show Password` button is used.\n\n### Patches\n`highlight.run@6.0.0` resolves the issue via https://github.com/rrweb-io/rrweb/pull/1184\nThis patch tracks changes to the `type` attribute of an input to ensure an input that used to be a `type=\"password\"` continues to be obfuscated. \n\n### Workarounds\nWe have deployed a change to our data ingest to obfuscate passwords server side from older clients.\nThis means that upgrading to the latest version of highlight.run is not necessary but recommended to prevent potential network transfer of recorded password data to our backend.\n\n### References\nhttps://github.com/rrweb-io/rrweb/pull/1184\n",
  "id": "GHSA-9qpj-qq2r-5mcc",
  "modified": "2023-05-26T13:52:19Z",
  "published": "2023-05-26T13:52:19Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/highlight/highlight/security/advisories/GHSA-9qpj-qq2r-5mcc"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-33187"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rrweb-io/rrweb/pull/1184"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/highlight/highlight"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "html inputs of type password recorded in plaintext when converted to text inputs"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.