Security
Headlines
HeadlinesLatestCVEs

Source

ghsa

GHSA-mg5h-rhjq-6v84: phpMyFAQ vulnerable to reflected Cross-site Scripting

phpMyFAQ prior to version 3.1.8 is vulnerable to reflected cross-site scripting.

ghsa
#xss#git#php
GHSA-wr74-2v66-57pp: phpMyFAQ vulnerable to stored Cross-site Scripting

phpMyFAQ prior to version 3.1.8 is vulnerable to stored Cross-site Scripting.

GHSA-2rr3-rv49-p42f: phpMyFAQ contains Weak Password Requirements

phpMyFAQ prior to version 3.1.8 has Weak Password Requirements. Version 3.1.8 introduces an eight-character minimum password length.

GHSA-5qxq-vgmm-q39m: RCE vulnerability in Pimcore/Mail & Dynamic Text Layout

### Impact The user controlled twig templates rendering in `Pimcore/Mail` & `ClassDefinition\Layout\Text` is vulnerable to server-side template Injection RCE. ### Patches Update to version 10.5.9 or apply this patch manually https://github.com/pimcore/pimcore/pull/13347.patch ### Workarounds Apply https://github.com/pimcore/pimcore/pull/13347.patch manually. ### References Credits: @nth347 from Viettel Cyber Security

GHSA-hff2-x2j9-gxgv: Keylime: unhandled exceptions could lead to invalid attestation states

### Impact This vulnerability creates a false sense of security for keylime users -- i.e. a user could query keylime and conclude that a parcitular node/agent is correctly attested, while attestations are not in fact taking place. **Short explanation**: the keylime verifier creates periodic reports on the state of each attested agent. The keylime verifier runs a set of python asynchronous processes to challenge attested nodes and create reports on the outcome. The vulnerability consists of the above named python asynchronous processes failing silently, i.e. quitting without leaving behind a database entry, raising an error or producing even a mention of an error in a log. The silent failure can be triggered by a small set of transient network failure conditions; recoverable device driver crashes being one such condition we saw in the wild. ### Patches The problem is fixed in keylime starting with tag 6.5.1 ### Workarounds This [patch](https://github.com/keylime/keylime/pull/112...

GHSA-vpgf-fgm8-gxr2: Apache DolphinScheduler vulnerable to Path Traversal

Users can read any files by log server, Apache DolphinScheduler users should upgrade to version 2.0.6 or higher.

GHSA-xqv2-3vvq-qg6r: Hashicorp Boundary vulnerable to clickjacking

Hashicorp Boundary is vulnerable to Clickjacking which allow for the interception of login credentials, re-direction of users to malicious sites, or causing users to perform malicious actions on the site.

GHSA-3fh5-q6fg-w28q: Prototype pollution in Snowboard framework

### Impact The Snowboard framework in affected versions is vulnerable to prototype pollution in the main Snowboard class as well as its plugin loader. ### Patches This issue has been patched in https://github.com/wintercms/winter/commit/2a13faf99972e84c9661258f16c4750fa99d29a1 (for 1.2) and https://github.com/wintercms/winter/commit/bce4b59584abf961e9400af3d7a4fd7638e26c7f (for 1.1) and is available with Winter v1.1.10 and v1.2.1. ### Workarounds If you have not yet upgraded, or are using the 1.1 branch of Winter (1.1.8 or above), you can avoid this issue by following some common security practices for JavaScript, including implementing a [content security policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) and auditing your scripts. The 1.0 branch of Winter is not affected, as it does not contain the Snowboard framework. ### For more information If you have any questions or comments about this advisory: - Email us at [[email protected]](mailto:[email protected]...

GHSA-jw36-mrvg-j5fx: Rdiffweb subject to Business Logic Errors

Business Logic Errors in GitHub repository ikus060/rdiffweb prior to 2.5.0a7.

GHSA-9chr-4fjh-5rgw: Cross-site Scripting in actionpack

actionpack from the Ruby on Rails project is vulnerable to Cross-site Scripting in the Route Error Page. This issue has been patched with this [commit](https://github.com/rails/rails/commit/be177e4566747b73ff63fd5f529fab564e475ed4). There are no known workarounds for this issue.