From nobody Mon Mar 07 17:23:17 2022 X-Original-To: dev-commits-ports-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B20B41A0D82E; Mon, 7 Mar 2022 17:23:17 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KC4zn4TMLz4qFr; Mon, 7 Mar 2022 17:23:17 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1646673797; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=qETRqEbHTmdM67AdL8AbW6VPz9NAU/VFOKUsoPgwz3c=; b=B+ao7OX2MLA2s3ZjobyQSfGwvJV87syhXtqETY+THi3nv39+rUa0KQNkf0I5RVvVdVcHty x4UWxGmiHyJtlmN6DZrlm8t34WyKVR0yBU5Zk2a8nTqtIsh09Yj14+U+0K1Afdauopyfxq czra8OpYdbu5wAJrPXzAwJ8d4Qyq98vmTtCsMQFN0qJU3xnlpuMJCX2r+gtE9dhRxCrfVo DMENuoGhdq+01ofWXzkjryGNeqqMNwt5clFkdg50Dh8vW+TdxDSrsh1z389Abf8719+WVC 28lzU7WS7ntqEju+JtTuBRqJSemv8mhqLcrPxbr8pMTjtOo5JqnQ829J2azm8A== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7A6224749; Mon, 7 Mar 2022 17:23:17 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 227HNHcG085378; Mon, 7 Mar 2022 17:23:17 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 227HNHCE085376; Mon, 7 Mar 2022 17:23:17 GMT (envelope-from git) Date: Mon, 7 Mar 2022 17:23:17 GMT Message-Id: <202203071723.227HNHCE085376@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: Neel Chauhan Subject: git: 8d55457d6e33 - main - security/vuxml: add CVE entries related to www/glpi List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: nc X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 8d55457d6e333a68173be8f6ec18d1f6bb6644cf Auto-Submitted: auto-generated ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1646673797; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=qETRqEbHTmdM67AdL8AbW6VPz9NAU/VFOKUsoPgwz3c=; b=oCCeLpB/S6L86HQITgM/wI7HsgjB4Ie5T8YKSBrDxsePbzcQ5G13N/TkoILaRDJOxiErvZ GIbjSx5rXohB3274sIMXUZhhvY9Iuf1SLzJTesPULH6IxUyQW+4Er1HsnwRb+H81D61t8j tx3Zjip+XCq91XPdb7lUkAK9u7MLGbiLDZigTFUOU7rzzfwkJf9ksHue7caklXB1JJShVN gZMW1QA2H7nMhsbIeB8B+UTtWKVuBuP5Cf7xFjXJ0LIZw5+rynrKv5Ikxn63KJKCFB2hVD ccDbf+5VXnFlWr02nBk2wOx+iNVXmoEQ6DBlmvAAdFwPJPpCcsMRDFpl8kC7VQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1646673797; a=rsa-sha256; cv=none; b=N4z8AVm2hBuKmdXK/MIZlKnPiIR4c/DzXyh5Mgp5h0QiyxoJFr6/HEyhbkUtTU3t7tmNqD zCp1X0IH4rz0jcNCsmEQLd2BKm3e/318OSoF4q+C9qJEQRVPeyfASR3rpxBYEIZK09CLXt y5eLWN0bgZOQe8itT5uB2MDgBjrPa19oRjTpf2ys6VnZ4fjEGI7OwrmAhIJrYJpbr4pC+S c5dANbNiZEB6fsBjllCH6AErWuTzm/yDkD+oTOxqcVKv8rcaDM8B/kJJlz2H1Uzn16u4h2 BwShubRIO8bJtbqB6yxo1ZIx+AM1IMcPYwRorIIcQ892b9DcWssnMHgyzKbDqA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by nc: URL: https://cgit.FreeBSD.org/ports/commit/?id=8d55457d6e333a68173be8f6ec18d1f6bb6644cf commit 8d55457d6e333a68173be8f6ec18d1f6bb6644cf Author: Mathias Monnerville AuthorDate: 2022-03-07 17:22:33 +0000 Commit: Neel Chauhan CommitDate: 2022-03-07 17:23:07 +0000 security/vuxml: add CVE entries related to www/glpi PR: 255948 --- security/vuxml/vuln-2022.xml | 529 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 529 insertions(+) diff --git a/security/vuxml/vuln-2022.xml b/security/vuxml/vuln-2022.xml index 69de14c1d2c9..39ae5abc51d8 100644 --- a/security/vuxml/vuln-2022.xml +++ b/security/vuxml/vuln-2022.xml @@ -1,3 +1,532 @@ + + + glpi -- Public GLPIKEY can be used to decrypt any data + + + glpi + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 + https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c + CVE-2020-5248 + + + 2020-01-02 + 2020-01-02 + + + + + glpi -- Insecure Direct Object Reference on ajax/getDropdownValue.php + + + glpi + 9.5.3 + + + + +

MITRE Corporation reports:

+
+

In GLPI before 9.5.3, ajax/getDropdownValue.php has an Insecure Direct Object Reference (IDOR) vulnerability that allows an attacker to read data from any itemType (e.g., Ticket, Users, etc.).

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-pqfv-4pvr-55r4 + CVE-2020-27663 + + + 2020-10-22 + 2020-10-22 + + + + + glpi -- Insecure Direct Object Reference on ajax/comments.ph + + + glpi + 9.5.3 + + + + +

MITRE Corporation reports:

+
+

In GLPI before 9.5.3, ajax/comments.php has an Insecure Direct Object Reference (IDOR) vulnerability that allows an attacker to read data from any database table (e.g., glpi_tickets, glpi_users, etc.).

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-wq38-gwxp-8p5p + CVE-2020-27662 + + + 2020-10-22 + 2020-10-22 + + + + + glpi -- Any CalDAV calendars is read-only for every authenticated user + + + glpi + 9.5.0 + 9.5.3 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.3, any authenticated user has read-only permissions to the planning of every other user, even admin ones. This issue is fixed in version 9.5.3. As a workaround, one can remove the caldav.php file to block access to CalDAV server.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-qmw3-87hr-5wgx + https://github.com/glpi-project/glpi/commit/527280358ec78988ac57e9809d2eb21fcd74caf7 + https://github.com/glpi-project/glpi/releases/tag/9.5.3 + CVE-2020-26212 + + + 2020-10-01 + 2020-10-01 + + + + + glpi -- SQL Injection in Search API + + + glpi + 9.1 + 9.5.2 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.2, there is a SQL Injection in the API's search function. Not only is it possible to break the SQL syntax, but it is also possible to utilise a UNION SELECT query to reflect sensitive information such as the current database version, or database user. The most likely scenario for this vulnerability is with someone who has an API account to the system. The issue is patched in version 9.5.2. A proof-of-concept with technical details is available in the linked advisory.

+
+ + + + https://github.com/glpi-project/glpi/commit/3dc4475c56b241ad659cc5c7cb5fb65727409cf0 + https://github.com/glpi-project/glpi/security/advisories/GHSA-jwpv-7m4h-5gvc + CVE-2020-15226 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- leakage issue with knowledge base + + + glpi + 9.5.0 + 9.5.2 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.2, there is a leakage of user information through the public FAQ. The issue was introduced in version 9.5.0 and patched in 9.5.2. As a workaround, disable public access to the FAQ.

+
+ + + + https://github.com/glpi-project/glpi/commit/39e25591efddc560e3679ab07e443ee6198705e2 + https://github.com/glpi-project/glpi/security/advisories/GHSA-x9hg-j29f-wvvv + CVE-2020-15217 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- Unauthenticated Stored XSS + + + glpi + 0.65 + 9.5.2 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.2, the `install/install.php` endpoint insecurely stores user input into the database as `url_base` and `url_base_api`. These settings are referenced throughout the application and allow for vulnerabilities like Cross-Site Scripting and Insecure Redirection Since authentication is not required to perform these changes,anyone could point these fields at malicious websites or form input in a way to trigger XSS. Leveraging JavaScript it's possible to steal cookies, perform actions as the user, etc. The issue is patched in version 9.5.2.

+
+ + + + https://github.com/glpi-project/glpi/commit/a8109d4ee970a222faf48cf48fae2d2f06465796 + https://github.com/glpi-project/glpi/security/advisories/GHSA-prvh-9m4h-4m79 + CVE-2020-15177 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- Multiple SQL Injections Stemming From isNameQuoted() + + + glpi + 0.68 + 9.5.2 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.2, when supplying a back tick in input that gets put into a SQL query,the application does not escape or sanitize allowing for SQL Injection to occur. Leveraging this vulnerability an attacker is able to exfiltrate sensitive information like passwords, reset tokens, personal details, and more. The issue is patched in version 9.5.2

+
+ + + + https://github.com/glpi-project/glpi/commit/f021f1f365b4acea5066d3e57c6d22658cf32575 + https://github.com/glpi-project/glpi/security/advisories/GHSA-x93w-64x9-58qw + CVE-2020-15176 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- Unauthenticated File Deletion + + + glpi + 0.70 + 9.5.2 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.2, the pluginimage.send.php endpoint allows a user to specify an image from a plugin. The parameters can be maliciously crafted to instead delete the .htaccess file for the files directory. Any user becomes able to read all the files and folders contained in /files/. Some of the sensitive information that is compromised are the user sessions, logs, and more. An attacker would be able to get the Administrators session token and use that to authenticate. The issue is patched in version 9.5.2.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-rm52-jx9h-rwcp + https://github.com/glpi-project/glpi/commit/6ca9a0e77299a755c356d758344a23278df67f65 + CVE-2020-15175 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- SQL injection for all usages of "Clone" feature + + + glpi + 9.5.0 + 9.5.1 + + + + +

MITRE Corporation reports:

+
+

In glpi before 9.5.1, there is a SQL injection for all usages of "Clone" feature. This has been fixed in 9.5.1.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-qv6w-68gq-wx2v + https://github.com/glpi-project/glpi/commit/a4baa64114eb92fd2adf6056a36e0582324414ba + https://github.com/glpi-project/glpi/pull/6684 + CVE-2020-15108 + + + 2020-06-25 + 2020-06-25 + + + + + glpi -- Reflexive XSS in Dropdown menus + + + glpi + 0.68.1 + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI after 0.68.1 and before 9.4.6, multiple reflexive XSS occur in Dropdown endpoints due to an invalid Content-Type. This has been fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-3xxh-f5p2-jg3h + https://github.com/glpi-project/glpi/commit/5e1c52c5e8a30ceb4e9572964da7ed89ddfb1aaf + CVE-2020-11062 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- Remote Code Execution (RCE) via the backup functionality + + + glpi + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI before 9.4.6, an attacker can execute system commands by abusing the backup functionality. Theoretically, this vulnerability can be exploited by an attacker without a valid account by using a CSRF. Due to the difficulty of the exploitation, the attack is only conceivable by an account having Maintenance privileges and the right to add WIFI networks. This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-cvvq-3fww-5v6f + https://github.com/glpi-project/glpi/commit/ad748d59c94da177a3ed25111c453902396f320c + CVE-2020-11060 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- multiple related stored XSS vulnerabilities + + + glpi + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.4.6 there are multiple related stored XSS vulnerabilities. The package is vulnerable to Stored XSS in the comments of items in the Knowledge base. Adding a comment with content "alert(1)" reproduces the attack. This can be exploited by a user with administrator privileges in the User-Agent field. It can also be exploited by an outside party through the following steps: 1. Create a user with the surname `" onmouseover="alert(document.cookie)` and an empty first name. 2. With this user, create a ticket 3. As an administrator (or other privileged user) open the created ticket 4. On the "last update" field, put your mouse on the name of the user 5. The XSS fires This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-3g3h-rwhr-7385 + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5WQMONZRWLWOXMHMYWR7A5Q5JJERPMVC/ + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q4BG2UTINBVV7MTJRXKBQ26GV2UINA6L/ + CVE-2020-11036 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- weak csrf tokens + + + glpi + 0.83.3 + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-w7q8-58qp-vmpf + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5WQMONZRWLWOXMHMYWR7A5Q5JJERPMVC/ + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q4BG2UTINBVV7MTJRXKBQ26GV2UINA6L/ + CVE-2020-11035 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- bypass of the open redirect protection + + + glpi + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.4.6, there is a vulnerability that allows bypassing the open redirect protection based which is based on a regexp. This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-gxv6-xq9q-37hg + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5WQMONZRWLWOXMHMYWR7A5Q5JJERPMVC/ + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q4BG2UTINBVV7MTJRXKBQ26GV2UINA6L/ + CVE-2020-11034 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- able to read any token through API user endpoint + + + glpi + 9.1 + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an application token. This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-rf54-3r4w-4h55 + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5WQMONZRWLWOXMHMYWR7A5Q5JJERPMVC/ + https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q4BG2UTINBVV7MTJRXKBQ26GV2UINA6L/ + CVE-2020-11033 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- SQL injection for all helpdesk instances + + + glpi + 9.4.6 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.4.6, there is a SQL injection vulnerability for all helpdesk instances. Exploiting this vulnerability requires a technician account. This is fixed in version 9.4.6.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-344w-34h9-wwhh + CVE-2020-11032 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- Improve encryption algorithm + + + glpi + 9.5.0 + + + + +

MITRE Corporation reports:

+
+

In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library chosen is sodium.

+
+ + + + https://github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh + https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780 + https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780 + CVE-2020-11031 + + + 2020-03-30 + 2020-03-30 + + + + + glpi -- Account takeover vulnerability + + + glpi + 9.4.4 + + + + +

MITRE Corporation reports:

+
+

GLPI through 9.4.3 is prone to account takeover by abusing the ajax/autocompletion.php autocompletion feature. The lack of correct validation leads to recovery of the token generated via the password reset functionality, and thus an authenticated attacker can set an arbitrary password for any user. This vulnerability can be exploited to take control of admin account. This vulnerability could be also abused to obtain other sensitive fields like API keys or password hashes.

+
+ + + + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14666 + https://github.com/glpi-project/glpi/security/advisories/GHSA-47hq-pfrr-jh5q + https://www.tarlogic.com/advisories/Tarlogic-2019-GPLI-Account-Takeover.txt + CVE-2019-14666 + + + 2019-08-05 + 2019-08-05 + + + asterisk -- multiple vulnerabilities