<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 12 Oct 2026 09:32:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-33187 — highlight vulnerable to cleartext transmission of sensitive information</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-33187</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; highlight&lt;/p&gt;
&lt;p&gt;Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type=&amp;#34;text&amp;#34;` via a javascript &amp;#34;Show Password&amp;#34; button. This differs from the expected behavior which always obfuscates `type=&amp;#34;password&amp;#34;` inputs. A customer may assume that switching to `type=&amp;#34;text&amp;#34;` 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. This issue was patched in version 6.0.0.
This patch tracks changes to the `type` attribute of an input to ensure an input that used to be a `type=&amp;#34;password&amp;#34;` continues to be obfuscated.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; highlight&lt;/p&gt;
&lt;p&gt;Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type=&amp;#34;text&amp;#34;` via a javascript &amp;#34;Show Password&amp;#34; button. This differs from the expected behavior which always obfuscates `type=&amp;#34;password&amp;#34;` inputs. A customer may assume that switching to `type=&amp;#34;text&amp;#34;` 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. This issue was patched in version 6.0.0.
This patch tracks changes to the `type` attribute of an input to ensure an input that used to be a `type=&amp;#34;password&amp;#34;` continues to be obfuscated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-33187</guid>
    </item>
  </channel>
</rss>
