<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T08:34:32.471959+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2024-39697</id>
    <title>CVE-2024-39697 — phonenumber panics on parsing crafted phonenumber inputs</title>
    <updated>2026-10-03T08:34:32.503469+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> whisperfish rust-phonenumber, whisperfish phonenumber</p>
<p>phonenumber is a library for parsing, formatting and validating international phone numbers. Since 0.3.4, the phonenumber parsing code may panic due to a panic-guarded out-of-bounds access on the phonenumber string. In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form `+dwPAA;phone-context=AA`, where the "number" part potentially parses as a number larger than 2^56. This vulnerability is fixed in 0.3.6.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-39697"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mjw4-jj88-v687</id>
    <title>GHSA-mjw4-jj88-v687 — panic on parsing crafted phonenumber inputs</title>
    <updated>2026-10-03T08:34:32.503530+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: phonenumber</p>
<p>### Impact
The phonenumber parsing code may panic due to a reachable `assert!` guard on the phonenumber string.</p>
<p>In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form `+dwPAA;phone-context=AA`, where the "number" part potentially parses as a number larger than 2^56.</p>
<p>Since f69abee1/0.3.4/#52.</p>
<p>0.2.x series is not affected.</p>
<p>### Patches
Upgrade to 0.3.6 or higher.</p>
<p>### Workarounds
n/a</p>
<p>### References
Whereas https://github.com/whisperfish/rust-phonenumber/issues/69 did not provide an example code path, property testing found a few: `+dwPAA;phone-context=AA`.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mjw4-jj88-v687"/>
  </entry>
</feed>
