<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T15:09:28.903537+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-46233</id>
    <title>CVE-2023-46233 — crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard</title>
    <updated>2026-09-29T15:09:30.102387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> brix crypto-js</p>
<p>crypto-js is a JavaScript library of crypto standards. Prior to version 4.2.0, crypto-js PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 4.2.0 contains a patch for this issue. As a workaround, configure crypto-js to use SHA256 with at least 250,000 iterations.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-46233"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-6753-1</id>
    <title>USN-6753-1 — cryptojs vulnerability</title>
    <updated>2026-09-29T15:09:30.102545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: cryptojs, Ubuntu:Pro:18.04:LTS: cryptojs, Ubuntu:20.04:LTS: cryptojs, Ubuntu:Pro:22.04:LTS: cryptojs</p>
<p>Thomas Neil James Shadwell discovered that CryptoJS was using an insecure
cryptographic default configuration. A remote attacker could possibly use
this issue to expose sensitive information.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-6753-1"/>
  </entry>
</feed>
