CVE-2011-1939 : SQL injection vulnerability in Zend Framework 1.10.x before 1.10.9 and 1.11.x before 1.11.6 when using non-ASCII-compati

SQL injection vulnerability in Zend Framework 1.10.x before 1.10.9 and 1.11.x before 1.11.6 when using non-ASCII-compatible encodings in conjunction PDO_MySql in PHP before 5.3.6.

Published 2019-11-26 22:15:14

Updated 2019-12-10 16:48:27

Source Red Hat, Inc.

View at NVD, CVE.org

Vulnerability category: Sql Injection

Threat overview for CVE-2011-1939

Top countries where our scanners detected CVE-2011-1939

Top open port discovered on systems with this issue 80

IPs affected by CVE-2011-1939 33,801

Threat actors abusing to this issue? Yes

Find out if you^* are affected by CVE-2011-1939!

^*Directly or indirectly through your vendors, service providers and 3rd parties. Powered by attack surface intelligence from SecurityScorecard.

Exploit prediction scoring system (EPSS) score for CVE-2011-1939

EPSS FAQ

1.21%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 85 %

Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2011-1939

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
7.5	HIGH	AV:N/AC:L/Au:N/C:P/I:P/A:P	10.0	6.4	NIST
Access Vector: Network Access Complexity: Low Authentication: None Confidentiality Impact: Partial Integrity Impact: Partial Availability Impact: Partial
9.8	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H	3.9	5.9	NIST
Attack Vector: Network Attack Complexity: Low Privileges Required: None User Interaction: None Scope: Unchanged Confidentiality: High Integrity: High Availability: High

CWE ids for CVE-2011-1939

CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Assigned by: nvd@nist.gov (Primary)

References for CVE-2011-1939

https://security-tracker.debian.org/tracker/CVE-2011-1939

CVE-2011-1939
Third Party Advisory
https://access.redhat.com/security/cve/cve-2011-1939

Red Hat Customer Portal
Broken Link
http://security.gentoo.org/glsa/glsa-201408-01.xml

Zend Framework: SQL injection (GLSA 201408-01) — Gentoo security
Third Party Advisory
http://www.securityfocus.com/bid/47919

Zend Framework 'PDO_MySql' Security Bypass Vulnerability
Third Party Advisory;VDB Entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-1939

709394 – (CVE-2011-1939) CVE-2011-1939 php-ZendFramework: potential SQL injection vector when using PDO_MySql (ZF2011-02)
Issue Tracking;Third Party Advisory
https://framework.zend.com/security/advisory/ZF2011-02

Security Advisory - Security - Zend Framework
Vendor Advisory
https://bugs.php.net/bug.php?id=47802

PHP :: Bug #47802 :: PDO_MYSQL doesn't use the charset parameter
Exploit;Third Party Advisory

Products affected by CVE-2011-1939