Security
Headlines
HeadlinesLatestCVEs

Source

ghsa

GHSA-v4gr-v679-42p7: PrestaShop file deletion via CustomerMessage

### Impact It is possible to delete files from the server via the CustomerMessage API ### Patches 8.1.1 ### Found by Kto94 (via Yeswehack) ### Workarounds none ### References none

ghsa
#vulnerability#git
GHSA-2rf5-3fw8-qm47: PrestaShop file deletion via attachment API

### Impact It is possible to delete a file from the server by using the Attachments controller and the Attachments API. ### Patches 8.1.1 ### Found by Kto94 (via Yeswehack) ### Workarounds none ### References none

GHSA-hpf4-v7v2-95p2: PrestaShop file access through path traversal

### Impact `displayAjaxEmailHTML` method can be used to read any file on the server, potentially even outside of the project if the server is not correctly configured ### Patches 8.1.1 ### Found by Aleksey Solovev (Positive Technologies) ### Workarounds ### References

GHSA-xw2r-f8xv-c8xp: PrestaShop XSS injection through Validate::isCleanHTML method

### Impact xss injection through `isCleanHTML` method ### Patches 1.7.8.10 8.0.5 8.1.1 ### Found by Aleksey Solovev (Positive Technologies) ### Workarounds ### References

GHSA-gf46-prm4-56pc: PrestaShop SQL manager vulnerability

### Impact Remote code execution through SQL injection and arbitrary file write in back office ### Patches 1.7.8.10 8.0.5 8.1.1 ### Found by Truff (via yeswehack) ### Workarounds none ### References none

GHSA-m9r4-3fg7-pqm2: PrestaShop path traversal

### Impact In the back office, files can be compromised using path traversal by replaying the import file deletion query with a specified file path, using traversal path. ### Patches 8.1.1 ### Found by Aleksey Solovev (Positive Technologies) ### Workarounds none ### References none

GHSA-75p5-jwx4-qw9h: PrestaShop boolean SQL injection

### Impact SQL injection possible in product search field, in BO's product page ### Patches 8.1.1 ### Found by Aleksey Solovev (Positive Technologies) ### Workarounds none ### References none

GHSA-5824-cm3x-3c38: Vyper has incorrectly allocated named re-entrancy locks

### Impact In versions 0.2.15, 0.2.16 and 0.3.0, named re-entrancy locks are allocated incorrectly. Each function using a named re-entrancy lock gets a unique lock regardless of the key, allowing cross-function re-entrancy in contracts compiled with the susceptible versions. A specific set of conditions is required to result in misbehavior of affected contracts, specifically: - A `.vy` contract compiled with either of the following `vyper` versions: `0.2.15`, `0.2.16`, `0.3.0` - A primary function that utilizes the `@nonreentrant` decorator with a specific `key` and does not strictly follow the check-effects-interaction pattern (i.e. contains an external call to an untrusted party before storage updates) - A secondary function that utilizes the same `key` and would be affected by the improper state caused by the primary function ### Patches https://github.com/vyperlang/vyper/pull/2439, https://github.com/vyperlang/vyper/pull/2514 ### Workarounds Upgrade to 0.3.1 or higher ### Refe...

GHSA-876p-8259-xjgg: libp2p nodes vulnerable to attack using large RSA keys

### Impact A malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p now restricts RSA keys to <= 8192 bits. ### Patches Users should upgrade their go-libp2p versions to >=v0.27.8, >= v0.28.2, or >=v0.29.1 To protect your application, it's necessary to update to these patch releases **AND** to use the updated Go compiler (1.20.7 or 1.19.12, respectively) ### Workarounds There are no known workarounds ### References The Golang crypto/tls package also had this vulnerability ("verifying certificate chains containing large RSA keys is slow” https://github.com/golang/go/issues/61460) Fix in golang/go crypto/tls: https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017 Fix in quic-go htt...

GHSA-c3x7-354f-4p2x: lol-html panics on certain HTML inputs

### Impact lol-html can cause panics on certain HTML inputs. Anyone processing arbitrary 3rd party HTML with the library is affected. ### Patches The problem has been patched and released as v1.1.1 ### Workarounds No workarounds exist.