<?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 comments.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent comments.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 17 Sep 2026 09:59:37 +0000</lastBuildDate>
    <item>
      <title>Apache Pinot Improper Neutralization of Special Elements Authentication Bypass Vulnerability</title>
      <link>https://vulnerability.circl.lu/comment/a9f2cad3-dbfc-4703-9c5f-9af054301f88</link>
      <description>CVE ID	CVE-2024-56325
CVSS SCORE	9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AFFECTED VENDORS	Apache
AFFECTED PRODUCTS	Pinot
VULNERABILITY DETAILS	
This vulnerability allows remote attackers to bypass authentication on affected installations of Apache Pinot. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the AuthenticationFilter class. The issue results from insufficient neutralization of special characters in a URI. An attacker can leverage this vulnerability to bypass authentication on the system.

ADDITIONAL DETAILS	
Fixed in version 1.3.0</description>
      <content:encoded>CVE ID	CVE-2024-56325
CVSS SCORE	9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AFFECTED VENDORS	Apache
AFFECTED PRODUCTS	Pinot
VULNERABILITY DETAILS	
This vulnerability allows remote attackers to bypass authentication on affected installations of Apache Pinot. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the AuthenticationFilter class. The issue results from insufficient neutralization of special characters in a URI. An attacker can leverage this vulnerability to bypass authentication on the system.

ADDITIONAL DETAILS	
Fixed in version 1.3.0</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/comment/a9f2cad3-dbfc-4703-9c5f-9af054301f88</guid>
      <pubDate>Tue, 11 Mar 2025 05:25:53 +0000</pubDate>
    </item>
    <item>
      <title>PoC - AMD EPYC 7B13 64-Core Processor (Milan) and AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (Phoenix).</title>
      <link>https://vulnerability.circl.lu/comment/4479dea7-72fb-4d91-90f4-95ffec3e0310</link>
      <description>- [PoC Tested on AMD EPYC 7B13 64-Core Processor (Milan) and AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (Phoenix).](https://github.com/google/security-research/tree/master/pocs/cpus/entrysign)

We've provided these PoCs to demonstrate that this vulnerability allows an adversary to produce arbitrary microcode patches. They cause the RDRAND instruction to always return the constant 4, but also set the carry flag (CF) to 0 to indicate that the returned value is invalid. Because correct use of the RDRAND instruction requires checking that CF is 1, this PoC can not be used to compromise correctly functioning confidential computing workloads. Additional tools and resources will be made public on March 5.</description>
      <content:encoded>- [PoC Tested on AMD EPYC 7B13 64-Core Processor (Milan) and AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (Phoenix).](https://github.com/google/security-research/tree/master/pocs/cpus/entrysign)

We've provided these PoCs to demonstrate that this vulnerability allows an adversary to produce arbitrary microcode patches. They cause the RDRAND instruction to always return the constant 4, but also set the carry flag (CF) to 0 to indicate that the returned value is invalid. Because correct use of the RDRAND instruction requires checking that CF is 1, this PoC can not be used to compromise correctly functioning confidential computing workloads. Additional tools and resources will be made public on March 5.</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/comment/4479dea7-72fb-4d91-90f4-95ffec3e0310</guid>
      <pubDate>Wed, 05 Feb 2025 07:31:30 +0000</pubDate>
    </item>
  </channel>
</rss>
