<?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>Tue, 06 Oct 2026 13:47:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326670</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326670</link>
      <description>EUVD-2026-326670</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326670</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42568</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42568</link>
      <description>&lt;p&gt;Yamcs is a mission control framework. Prior to versions 5.13.0 and 5.12.7, an LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` when constructing search filters. The username parameter is inserted directly into the LDAP filter without proper RFC 4515 escaping. Versions 5.13.0 and 5.12.7 patch the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Yamcs is a mission control framework. Prior to versions 5.13.0 and 5.12.7, an LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` when constructing search filters. The username parameter is inserted directly into the LDAP filter without proper RFC 4515 escaping. Versions 5.13.0 and 5.12.7 patch the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42568</guid>
    </item>
    <item>
      <title>GHSA-cqh3-jg8p-336j — Yamcs Vulnerable to LDAP Injection in LdapAuthModule</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cqh3-jg8p-336j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.yamcs:yamcs-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` when constructing search filters. The username parameter is inserted directly into the LDAP filter without proper RFC 4515 escaping.&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;**File:** `yamcs-core/src/main/java/org/yamcs/security/LdapAuthModule.java:233`&lt;/p&gt;
&lt;p&gt;The `username` parameter is inserted directly into an LDAP search filter without RFC 4515 escaping:&lt;/p&gt;
&lt;p&gt;```java
// VULNERABLE
var filter = userFilter.replace(&amp;#34;{0}&amp;#34;, username);
var searchResult = getSingleResult(ctx, userBase, filter, controls);
```&lt;/p&gt;
&lt;p&gt;LDAP wildcard characters (`*`, `(`, `)`) are accepted without sanitization.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With a known valid password, `username=*` authenticates as the first user returned by the LDAP search — enabling horizontal privilege escalation between accounts sharing similar passwords or when the attacker knows one valid password.&lt;/p&gt;
&lt;p&gt;This affects deployments that use `org.yamcs.security.LdapAuthModule` in their `etc/security.yaml` configuration file.&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```bash
curl -X POST &amp;#34;http://TARGET:8090/auth/token&amp;#34; \
  -d &amp;#34;grant_type=password&amp;amp;username=*&amp;amp;password=known_password&amp;#34;
# Returns token for first matching LDAP user
```&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Apply RFC 4515 escaping before filter construction:&lt;/p&gt;
&lt;p&gt;```java
private static String escapeLdapFilter(String input) {
    return input
        .replace(&amp;#34;\\&amp;#34;, &amp;#34;\\5c&amp;#34;)
        .replace(&amp;#34;*&amp;#34;,  &amp;#34;\\2a&amp;#34;)
        .replace(&amp;#34;(&amp;#34;,  &amp;#34;\\28&amp;#34;)
        .replace(&amp;#34;)&amp;#34;,  &amp;#34;\\29&amp;#34;)
        .replace(&amp;#34;\0&amp;#34;, &amp;#34;\\00&amp;#34;)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.yamcs:yamcs-core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` when constructing search filters. The username parameter is inserted directly into the LDAP filter without proper RFC 4515 escaping.&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;**File:** `yamcs-core/src/main/java/org/yamcs/security/LdapAuthModule.java:233`&lt;/p&gt;
&lt;p&gt;The `username` parameter is inserted directly into an LDAP search filter without RFC 4515 escaping:&lt;/p&gt;
&lt;p&gt;```java
// VULNERABLE
var filter = userFilter.replace(&amp;#34;{0}&amp;#34;, username);
var searchResult = getSingleResult(ctx, userBase, filter, controls);
```&lt;/p&gt;
&lt;p&gt;LDAP wildcard characters (`*`, `(`, `)`) are accepted without sanitization.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;With a known valid password, `username=*` authenticates as the first user returned by the LDAP search — enabling horizontal privilege escalation between accounts sharing similar passwords or when the attacker knows one valid password.&lt;/p&gt;
&lt;p&gt;This affects deployments that use `org.yamcs.security.LdapAuthModule` in their `etc/security.yaml` configuration file.&lt;/p&gt;
&lt;p&gt;### Proof of Concept&lt;/p&gt;
&lt;p&gt;```bash
curl -X POST &amp;#34;http://TARGET:8090/auth/token&amp;#34; \
  -d &amp;#34;grant_type=password&amp;amp;username=*&amp;amp;password=known_password&amp;#34;
# Returns token for first matching LDAP user
```&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;Apply RFC 4515 escaping before filter construction:&lt;/p&gt;
&lt;p&gt;```java
private static String escapeLdapFilter(String input) {
    return input
        .replace(&amp;#34;\\&amp;#34;, &amp;#34;\\5c&amp;#34;)
        .replace(&amp;#34;*&amp;#34;,  &amp;#34;\\2a&amp;#34;)
        .replace(&amp;#34;(&amp;#34;,  &amp;#34;\\28&amp;#34;)
        .replace(&amp;#34;)&amp;#34;,  &amp;#34;\\29&amp;#34;)
        .replace(&amp;#34;\0&amp;#34;, &amp;#34;\\00&amp;#34;)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cqh3-jg8p-336j</guid>
    </item>
  </channel>
</rss>
