GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-65mj-7c86-79jfcritical9.1

Authentication Bypass in ADOdb/ADOdb

Check your stack

The advisory, in context

Impact

An attacker can inject values into a PostgreSQL connection string by providing a parameter surrounded by single quotes.

Depending on how the library is used in the client software, this may allow an attacker to bypass the login process, gain access to the server's IP address, etc.

Patches

The vulnerability is fixed in ADOdb versions 5.20.21 (952de6c4273d9b1e91c2b838044f8c2111150c29) and 5.21.4 or later (b4d5ce70034c5aac3a1d51d317d93c037a0938d2).

The simplest patch is to delete line 29 in drivers/adodb-postgres64.inc.php:

diff --git a/drivers/adodb-postgres64.inc.php b/drivers/adodb-postgres64.inc.php
index d04b7f67..729d7141 100644
--- a/drivers/adodb-postgres64.inc.php
+++ b/drivers/adodb-postgres64.inc.php
@@ -26,7 +26,6 @@ function adodb_addslashes($s)
 {
    $len = strlen($s);
    if ($len == 0) return "''";
-   if (strncmp($s,"'",1) === 0 && substr($s,$len-1) == "'") return $s; // already quoted
 
    return "'".addslashes($s)."'";
 }

Workarounds

Ensure the parameters passed to ADOConnection::connect() or related functions (nConnect(), pConnect()) are not surrounded by single quotes.

Credits

Thanks to Emmet Leahy (@meme-lord) of Sorcery Ltd for reporting this vulnerability, and to the huntr team for their support.

References

For more information

If you have any questions or comments about this advisory:

  • Add a note in issue #793
  • Contact the maintainers on Gitter

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

Earlier releases before 5.20.21

Fixed in 5.20.21

22 explicitly affected versions

v5.19, v5.20.0, v5.20.1, v5.20.10, v5.20.11, v5.20.12, v5.20.13, v5.20.14, v5.20.15, v5.20.16, v5.20.17, v5.20.18, v5.20.19, v5.20.2, v5.20.20, v5.20.3, v5.20.4, v5.20.5, v5.20.6, v5.20.7, v5.20.8, v5.20.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "5.20.21"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v5.19",
    "v5.20.0",
    "v5.20.1",
    "v5.20.10",
    "v5.20.11",
    "v5.20.12",
    "v5.20.13",
    "v5.20.14",
    "v5.20.15",
    "v5.20.16",
    "v5.20.17",
    "v5.20.18",
    "v5.20.19",
    "v5.20.2",
    "v5.20.20",
    "v5.20.3",
    "v5.20.4",
    "v5.20.5",
    "v5.20.6",
    "v5.20.7",
    "v5.20.8",
    "v5.20.9"
  ]
}
Ecosystem versions

From 5.21.0 before 5.21.4

Fixed in 5.21.4

4 explicitly affected versions

v5.21.0, v5.21.1, v5.21.2, v5.21.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "5.21.0"
        },
        {
          "fixed": "5.21.4"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v5.21.0",
    "v5.21.1",
    "v5.21.2",
    "v5.21.3"
  ]
}

References