<?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>Fri, 09 Oct 2026 18:32:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-1524 — A local user can be impersonated when using federated authentication with Silent JIT Provisioning.</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-1524</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WSO2 API Manager, WSO2 Identity Server&lt;/p&gt;
&lt;p&gt;When the &amp;#34;Silent Just-In-Time Provisioning&amp;#34; feature is enabled for a federated identity provider (IDP)  there is a risk that a local user store user&amp;#39;s information may be replaced during the account provisioning process in cases where federated users share the same username as local users.&lt;/p&gt;
&lt;p&gt;There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted local user account with a federated IDP user account that they control.&lt;/p&gt;
&lt;p&gt;The Deployment should have: 
-An IDP configured for federated authentication with Silent JIT provisioning enabled.&lt;/p&gt;
&lt;p&gt;The malicious actor should have:
-A fresh valid user account in the federated IDP that has not been used earlier.
-Knowledge of the username of a valid user in the local IDP. 
-An account at the federated IDP matching the targeted local username.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WSO2 API Manager, WSO2 Identity Server&lt;/p&gt;
&lt;p&gt;When the &amp;#34;Silent Just-In-Time Provisioning&amp;#34; feature is enabled for a federated identity provider (IDP)  there is a risk that a local user store user&amp;#39;s information may be replaced during the account provisioning process in cases where federated users share the same username as local users.&lt;/p&gt;
&lt;p&gt;There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted local user account with a federated IDP user account that they control.&lt;/p&gt;
&lt;p&gt;The Deployment should have: 
-An IDP configured for federated authentication with Silent JIT provisioning enabled.&lt;/p&gt;
&lt;p&gt;The malicious actor should have:
-A fresh valid user account in the federated IDP that has not been used earlier.
-Knowledge of the username of a valid user in the local IDP. 
-An account at the federated IDP matching the targeted local username.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-1524</guid>
    </item>
  </channel>
</rss>
