<?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://db.gcve.eu</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>Thu, 01 Oct 2026 13:37:10 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-32599</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-32599</link>
      <description>&lt;p&gt;Netmaker makes networks with WireGuard. Prior to version 1.5.0, the `sqliteDeleteRecord` function in Netmaker&amp;#39;s database layer constructs SQL `DELETE` statements using direct string concatenation of user-supplied input. This allows an authenticated attacker to perform boolean-based SQL injection. Version 1.5.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Netmaker makes networks with WireGuard. Prior to version 1.5.0, the `sqliteDeleteRecord` function in Netmaker&amp;#39;s database layer constructs SQL `DELETE` statements using direct string concatenation of user-supplied input. This allows an authenticated attacker to perform boolean-based SQL injection. Version 1.5.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-32599</guid>
    </item>
    <item>
      <title>GHSA-r8cr-4f9w-7r75 — Netmaker has a boolean‑based SQL Injection</title>
      <link>https://db.gcve.eu/vuln/ghsa-r8cr-4f9w-7r75</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gravitl/netmaker&lt;/p&gt;
&lt;p&gt;# SQL Injection in Netmaker SQLite Database Backend&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `sqliteDeleteRecord` function in Netmaker&amp;#39;s database layer constructs SQL `DELETE` statements using direct string concatenation of user-supplied input. This allows an authenticated attacker to perform **boolean-based SQL injection**.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The endpoint:&lt;/p&gt;
&lt;p&gt;DELETE /api/dns/{network}/{domain}&lt;/p&gt;
&lt;p&gt;passes user-controlled path parameters through the following flow:&lt;/p&gt;
&lt;p&gt;logic.DeleteDNS → database.DeleteRecord → sqliteDeleteRecord&lt;/p&gt;
&lt;p&gt;Depending on the configured database backend, the request eventually reaches the SQLite database implementation.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code&lt;/p&gt;
&lt;p&gt;The SQL query is constructed using direct string concatenation without parameterization.&lt;/p&gt;
&lt;p&gt;```go
// database/sqlite.go
deleteSQL := &amp;#34;DELETE FROM &amp;#34; + tableName + &amp;#34; WHERE key = \&amp;#34;&amp;#34; + key + &amp;#34;\&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;The key value originates from user input ({domain} path parameter) and is embedded directly into the SQL query.&lt;/p&gt;
&lt;p&gt;Exploitation&lt;/p&gt;
&lt;p&gt;An authenticated attacker can inject SQL operators into the {domain} path parameter to manipulate the query logic.&lt;/p&gt;
&lt;p&gt;Because this injection is boolean-based, attackers extract data indirectly by observing the outcome of the operation:&lt;/p&gt;
&lt;p&gt;If the injected condition evaluates true, the DNS record is deleted.&lt;/p&gt;
&lt;p&gt;If the condition evaluates false, the DNS record remains.&lt;/p&gt;
&lt;p&gt;By repeating this process, an attacker can infer information such as:&lt;/p&gt;
&lt;p&gt;Database table names&lt;/p&gt;
&lt;p&gt;Column names&lt;/p&gt;
&lt;p&gt;Column values&lt;/p&gt;
&lt;p&gt;Value lengths&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;An authenticated attacker can…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/gravitl/netmaker&lt;/p&gt;
&lt;p&gt;# SQL Injection in Netmaker SQLite Database Backend&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `sqliteDeleteRecord` function in Netmaker&amp;#39;s database layer constructs SQL `DELETE` statements using direct string concatenation of user-supplied input. This allows an authenticated attacker to perform **boolean-based SQL injection**.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The endpoint:&lt;/p&gt;
&lt;p&gt;DELETE /api/dns/{network}/{domain}&lt;/p&gt;
&lt;p&gt;passes user-controlled path parameters through the following flow:&lt;/p&gt;
&lt;p&gt;logic.DeleteDNS → database.DeleteRecord → sqliteDeleteRecord&lt;/p&gt;
&lt;p&gt;Depending on the configured database backend, the request eventually reaches the SQLite database implementation.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code&lt;/p&gt;
&lt;p&gt;The SQL query is constructed using direct string concatenation without parameterization.&lt;/p&gt;
&lt;p&gt;```go
// database/sqlite.go
deleteSQL := &amp;#34;DELETE FROM &amp;#34; + tableName + &amp;#34; WHERE key = \&amp;#34;&amp;#34; + key + &amp;#34;\&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;The key value originates from user input ({domain} path parameter) and is embedded directly into the SQL query.&lt;/p&gt;
&lt;p&gt;Exploitation&lt;/p&gt;
&lt;p&gt;An authenticated attacker can inject SQL operators into the {domain} path parameter to manipulate the query logic.&lt;/p&gt;
&lt;p&gt;Because this injection is boolean-based, attackers extract data indirectly by observing the outcome of the operation:&lt;/p&gt;
&lt;p&gt;If the injected condition evaluates true, the DNS record is deleted.&lt;/p&gt;
&lt;p&gt;If the condition evaluates false, the DNS record remains.&lt;/p&gt;
&lt;p&gt;By repeating this process, an attacker can infer information such as:&lt;/p&gt;
&lt;p&gt;Database table names&lt;/p&gt;
&lt;p&gt;Column names&lt;/p&gt;
&lt;p&gt;Column values&lt;/p&gt;
&lt;p&gt;Value lengths&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;An authenticated attacker can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-r8cr-4f9w-7r75</guid>
    </item>
  </channel>
</rss>
