p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости zendframework/zendframework1

За последние 30 дней в zendframework/zendframework1 опубликовано уязвимостей: 0; в каталоге KEV: 0.

RSS ↗
Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 34

  1. GHSA-6fqw-j3vm-7f66

    Критический · CVSS 9.8Есть исправление

    Zendframework1 Potential SQL injection in ORDER and GROUP functions

    The implementation of ORDER BY and GROUP BY in Zend_Db_Select remained prone to SQL injection when a combination of SQL expressions and comments were used. This security patch provides a comprehensive solution that identifies and removes comments prior to checking validity of the statement to ensure no SQLi vectors occur. The implementation of ORDER BY and GROUP BY in Zend_Db_Select of ZF1 is vulnerable by the following SQL injection: ``` $db = Zend_Db::factory(/* options here */); $select = new Zend_Db_Select($db); $select->from('p'); $select->order("MD5(\"a(\");DELETE FROM p2; #)"); // same with group() ``` The above $select will render th

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.20
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  2. GHSA-848f-mph5-9pm9

    Высокий · CVSS 7.5Есть исправление

    Zendframework Potential Information Disclosure and Insufficient Entropy vulnerability

    In Zend Framework, Zend_Captcha_Word (v1) and Zend\Captcha\Word (v2) generate a "word" for a CAPTCHA challenge by selecting a sequence of random letters from a character set. Prior to this advisory, the selection was performed using PHP's internal array_rand() function. This function does not generate sufficient entropy due to its usage of rand() instead of more cryptographically secure methods such as openssl_pseudo_random_bytes(). This could potentially lead to information disclosure should an attacker be able to brute force the random number generation.

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.17
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  3. GHSA-8xhv-gqm4-3w99

    Высокий · CVSS 7.5Есть исправление

    ZendFramework1 Potential Insufficient Entropy Vulnerability

    We discovered several methods used to generate random numbers in ZF1 that potentially used insufficient entropy. These random number generators are used in the following method calls: ``` Zend_Ldap_Attribute::createPassword Zend_Form_Element_Hash::_generateHash Zend_Gdata_HttpClient::filterHttpRequest Zend_Filter_Encrypt_Mcrypt::_srand Zend_OpenId::randomBytes ``` In each case, the methods were using rand() or mt_rand(), neither of which can generate cryptographically secure values. This could potentially lead to information disclosure should an attacker be able to brute force the random number generation. Moreover, we discovered a potential

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.18
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  4. GHSA-v42g-7q2x-cw32

    Критический · CVSS 9.8Есть исправление

    Zendframework1 potential SQL injection vector using null byte for PDO (MsSql, SQLite)

    The PDO adapters of Zend Framework 1 do not filter null bytes values in SQL statements. A PDO adapter can treat null bytes in a query as a string terminator, allowing an attacker to add arbitrary SQL following a null byte, and thus create a SQL injection. We tested and verified the null byte injection using pdo_dblib (FreeTDS) on a Linux environment to access a remote Microsoft SQL Server, and also tested against and noted the vector against pdo_sqlite.

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.16
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  5. GHSA-2x36-qhx3-7m5f

    Критический · CVSS 9.8Есть исправление

    ZendFramework1 Potential SQL injection in the ORDER implementation of Zend_Db_Select

    The implementation of the ORDER BY SQL statement in Zend_Db_Select of Zend Framework 1 contains a potential SQL injection when the query string passed contains parentheses. For instance, the following code is affected by this issue: ``` $db = Zend_Db::factory( /* options here */ ); $select = $db->select() ->from(array('p' => 'products')) ->order('MD5(1); drop table products'); echo $select; ``` This code produce the string: ``` SELECT "p".* FROM "products" AS "p" ORDER BY MD5(1);drop table products ASC ``` instead of the correct one: ``` SELECT "p".* FROM "products" AS "p" ORDER BY "MD5(1);drop table products" ASC ``` The SQL inj

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  6. GHSA-9v78-h226-2rmq

    Высокий · CVSS 7.5Есть исправление

    Zendframework potential security issue in login mechanism

    Using the Consumer component of ZendOpenId (or Zend_OpenId in ZF1), it is possible to login using an arbitrary OpenID account (without knowing any secret information) by using a malicious OpenID Provider. That means OpenID it is possible to login using arbitrary OpenID Identity (MyOpenID, Google, etc), which are not under the control of our own OpenID Provider. Thus, we are able to impersonate any OpenID Identity against the framework. Moreover, the Consumer accepts OpenID tokens with arbitrary signed elements. The framework does not check if, for example, both openid.claimed_id and openid.endpoint_url are signed. It is just sufficient to si

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.4
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  7. GHSA-4vf6-mq7w-3hp6

    Средний · CVSS 6.1Есть исправление

    Zend_Filter_StripTags vulnerable to Cross-site Scripting when comments allowed

    Zend_Filter_StripTags contained an optional setting to allow whitelisting HTML comments in filtered text. Microsoft Internet Explorer and several other browsers allow developers to create conditional functionality via HTML comments, including execution of script events and rendering of additional commented markup. By allowing whitelisting of HTML comments, a malicious user could potentially include XSS exploits within HTML comments that would then be rendered in the final output.

    zendframework/zendframework1 zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.7.9
    • Обновитесь до 1.8.5
    • Обновитесь до 1.9.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  8. GHSA-4v57-pwvf-x35j

    Средний · CVSS 6.1Есть исправление

    Zendframework potential Cross-site Scripting vector in `Zend_Service_ReCaptcha_MailHide`

    `Zend_Service_ReCaptcha_MailHide` had a potential XSS vulnerability. Due to the fact that the email address was never validated, and because its use of `htmlentities()` did not include the encoding argument, it was potentially possible for a malicious user aware of the issue to inject a specially crafted multibyte string as an attack via the CAPTCHA's email argument

    zendframework/zendframework1 zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.7.9
    • Обновитесь до 1.8.5
    • Обновитесь до 1.9.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  9. GHSA-vvm3-rv48-j3g5

    Средний · CVSS 6.1Есть исправление

    Zendframework Potential XSS or HTML Injection vector in Zend_Json

    `Zend_Json_Encoder` was not taking into account the solidus character (/) during encoding, leading to incompatibilities with the JSON specification, and opening the potential for XSS or HTML injection attacks when returning HTML within a JSON string.

    zendframework/zendframework1 zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.7.9
    • Обновитесь до 1.8.5
    • Обновитесь до 1.9.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  10. GHSA-w5mj-j45q-m638

    Без оценкиЕсть исправление

    ZendFramework1 Potential Security Issues in Bundled Dojo Library

    In mid-March, 2010, the Dojo Foundation issued a Security Advisory indicating potential security issues with specific files in Dojo Toolkit. Details of the advisory may be found on the Dojo website: http://dojotoolkit.org/blog/post/dylan/2010/03/dojo-security-advisory/ In particular, several files in the Dojo tree were identified as having potential exploits, and the Dojo team also advised disabling or removing any PHP scripts in the tree when deploying to production.

    zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.10.3
    • Обновитесь до 1.9.8
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  11. GHSA-229x-22xc-2f2w

    Высокий · CVSS 8.6Есть исправление

    Zendframework Local file disclosure via XXE injection in Zend_XmlRpc

    Zend_XmlRpc is vulnerable to XML eXternal Entity (XXE) Injection attacks. The SimpleXMLElement class (SimpleXML PHP extension) is used in an insecure way to parse XML data. External entities can be specified by adding a specific DOCTYPE element to XML-RPC requests. By exploiting this vulnerability an application may be coerced to open arbitrary files and/or TCP connections.

    zendframework/zendframework1PHP
    • Обновитесь до 1.11.13
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  12. GHSA-2jx7-xg83-j2m7

    Высокий · CVSS 7.5Есть исправление

    Zendframework Denial of Service vector via XEE injection

    `Zend_Dom`, `Zend_Feed`, `Zend_Soap`, and `Zend_XmlRpc` are vulnerable to XML Entity Expansion (XEE) vectors, leading to Denial of Service vectors. XEE attacks occur when the XML DOCTYPE declaration includes XML entity definitions that contain either recursive or circular references; this leads to CPU and memory consumption, making Denial of Service exploits trivial to implement.

    zendframework/zendframework1PHP
    • Обновитесь до 1.11.13
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  13. GHSA-gwpm-pm6x-h7rj

    Средний · CVSS 6.1Есть исправление

    ZendFramework Cross-site Scripting vector in `Zend_Filter_StripTags`

    `Zend_Filter_StripTags` is a filtering class analogous to PHP's `strip_tags()` function. In addition to stripping HTML tags and selectively keeping those provided in a whitelist, it also provides the ability to whitelist specific attributes to retain per whitelisted tag. The reporter discovered that attributes that contained whitespace, and in paricular, line breaks, surrounding the attribute assignment operator would not be stripped, regardless of whether or not they were whitelisted. As examples of input affected: ``` <!-- newlines before and/or after assignment: --> <a href="http://framework.zend.com/issues" onclick = "alert('Broken'); re

    zendframework/zendframework1PHP
    • Обновитесь до 1.7.6
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  14. GHSA-g52p-86j5-xr8q

    Средний · CVSS 6.1Есть исправление

    ZendFramework Potential Cross-site Scripting in Development Environment Error View Script

    The default error handling view script generated using `Zend_Tool` failed to escape request parameters when run in the "development" configuration environment, providing a potential XSS attack vector. `Zend_Tool_Project_Context_Zf_ViewScriptFile` was patched such that the view script template now calls the `escape()` method on dumped request variables. Zend Framework 1.11.4 includes a patch that adds escaping to the generated error/error.phtml view script, ensuring that request variables are escaped appropriately for the browser. Do note, however, that this will not update any previously generated code. You will still need to follow the nex

    zendframework/zendframework1PHP
    • Обновитесь до 1.11.4
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  15. GHSA-mhpx-3rv8-wrjm

    Критический · CVSS 9.8Есть исправление

    ZendFramework potential XML eXternal Entity injection vectors

    Numerous components utilizing PHP's `DOMDocument`, `SimpleXML`, and `xml_parse` functionality are vulnerable to two types of attacks: - XML eXternal Entity (XXE) Injection attacks. The above mentioned extensions are insecure by default, allowing external entities to be specified by adding a specific DOCTYPE element to XML documents and strings. By exploiting this vulnerability an application may be coerced to open arbitrary files and/or TCP connections. - XML Entity Expansion (XEE) vectors, leading to Denial of Service vectors. XEE attacks occur when the XML DOCTYPE declaration includes XML entity definitions that contain either recursive or

    zendframework/zendframework1PHP
    • Обновитесь до 1.12.4
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  16. GHSA-4j9x-g4x8-vcmf

    Высокий · CVSS 7.5Есть исправление

    ZendFramework potential XML eXternal Entity injection vectors

    `Zend_Feed_Rss` and `Zend_Feed_Atom` were found to contain potential XML eXternal Entity (XXE) vectors due to insecure usage of PHP's DOM extension. External entities could be specified by adding a specific DOCTYPE element to feeds; exploiting this vulnerability could coerce opening arbitrary files and/or TCP connections. A similar issue was fixed for 1.11.13 and 1.12.0, in the `Zend_Feed::import()` factory method; however, the reporter of the issue discovered that the individual classes contained similar functionality in their constructors which remained vulnerable.

    zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.11.15
    • Обновитесь до 1.12.1
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  17. GHSA-hg35-vqp3-fv39

    Средний · CVSS 6.1Есть исправление

    ZendFramework potential Cross-site Scripting vectors due to inconsistent encodings

    A number of classes, primarily within the `Zend_Form`, `Zend_Filter`, `Zend_Form`, `Zend_Log` and `Zend_View components`, contained character encoding inconsistencies whereby calls to the `htmlspecialchars()` and htmlentities() functions used undefined or hard coded charset parameters. In many of these cases developers were unable to set a character encoding of their choice. These inconsistencies could, in specific circumstances, allow certain multibyte representations of special HTML characters pass through unescaped leaving applications potentially vulnerable to cross-site scripting (XSS) exploits. Such exploits would only be possible if a

    zendframework/zendframework1PHP
    • Обновитесь до 1.9.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  18. GHSA-qf36-fx9f-232x

    Критический · CVSS 9.8Есть исправление

    ZendFramework potential SQL Injection Vector When Using PDO_MySql

    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

    zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.10.9
    • Обновитесь до 1.11.6
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  19. GHSA-j543-vg33-g6vj

    Средний · CVSS 6.1Есть исправление

    ZendFramework potential Cross-site Scripting vector in `Zend_Dojo_View_Helper_Editor`

    `Zend_Dojo_View_Helper_Editor` was incorrectly decorating a TEXTAREA instead of a DIV. The Dojo team has reported that this has security implications as the rich text editor they use is unable to escape content for a TEXTAREA.

    zendframework/zendframework1 zendframework/zendframework1 zendframework/zendframework1PHP
    • Обновитесь до 1.7.9
    • Обновитесь до 1.8.5
    • Обновитесь до 1.9.7
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  20. GHSA-hx3m-959f-v849

    Высокий · CVSS 7.5Есть исправление

    ZendFramework local file inclusion vector in `Zend_View::setScriptPath()` and `render()`

    Zend_View is a component that utilizes PHP as a templating language. To utilize it, you specify "script paths" that contain view scripts, and then `render()` view scripts by specifying subdirectories within those script paths; the output is then returned as a string value which may be cached or directly output. `Zend_View::setScriptPath()` in versions up to and including 1.7.4 include a potential Local File Inclusion vulnerability. If untrusted input is used to specify the script path and/or view script itself, a malicious attacker could potentially specify a system directory and thus render a system file. As an example, if the user-supplie

    zendframework/zendframework1PHP
    • Обновитесь до 1.7.5
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →