Skip to content
Noroxi
OSV ecosystem advisory

GHSA-qf36-fx9f-232x: ZendFramework potential SQL Injection Vector When Using PDO_MySql

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: zendframework/zendframework1 (Packagist) 1.10.9, 1.11.6.

Low priority for now. Upgrade to zendframework/zendframework1 (Packagist) 1.10.9, 1.11.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

Developers using non-ASCII-compatible encodings in conjunction with the MySQL PDO driver of PHP may be vulnerable to SQL injection attacks. Developers using ASCII-compatible encodings like UTF8 or latin1 are not affected by this PHP issue, which is described in more detail here: http://bugs.php.net/bug.php?id=47802 The PHP Group included a feature in PHP 5.3.6+ that allows any character set information to be passed as part of the DSN in PDO to allow both the database as well as the C-level driver to be aware of which charset is in use which is of special importance when PDO's quoting mechanisms are utilized, which Zend Framework also relies on.

Published
Jun 7, 2024
Updated
Jun 7, 2024
EPSS
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-qf36-fx9f-232x

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Packagistzendframework/zendframework1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistzendframework/zendframework1from 1.10.0 · before 1.10.91.10.9
Packagistzendframework/zendframework1from 1.11.0 · before 1.11.61.11.6

Other highest-scoring records for the same primary product.

  • GHSA-6fqw-j3vm-7f66Zendframework1 Potential SQL injection in ORDER and GROUP functions
    39Monitor
  • GHSA-v42g-7q2x-cw32Zendframework1 potential SQL injection vector using null byte for PDO (MsSql, SQLite)
    39Monitor
  • GHSA-2x36-qhx3-7m5fZendFramework1 Potential SQL injection in the ORDER implementation of Zend_Db_Select
    39Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-hx3m-959f-v849Jun 7, 2024 · ZendFramework local file inclusion vector in `Zend_View::setScriptPath()` and `render()`
    30Monitor
  • ← EarlierGHSA-j543-vg33-g6vjJun 7, 2024 · ZendFramework potential Cross-site Scripting vector in `Zend_Dojo_View_Helper_Editor`
    24Monitor
  • Later →GHSA-hg35-vqp3-fv39Jun 7, 2024 · ZendFramework potential Cross-site Scripting vectors due to inconsistent encodings
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:zendframework/zendframework11.10.9Package registry (OSV)
Packagist:zendframework/zendframework11.11.6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • GHSA-2x36-qhx3-7m5f0 days apartZendFramework1 Potential SQL injection in the ORDER implementation of Zend_Db_Select
    39Monitor
  • GHSA-6fqw-j3vm-7f660 days apartZendframework1 Potential SQL injection in ORDER and GROUP functions
    39Monitor
  • GHSA-v42g-7q2x-cw320 days apartZendframework1 potential SQL injection vector using null byte for PDO (MsSql, SQLite)
    39Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

osv

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

References

All records