Most recent entries from github

GHSA-89ch-hqf9-rgp3 — Using JS libraries with known security vulnerabilities

2019-11-15T20:11:29+00:00

Affected: Packagist: magento/community-edition, Packagist: magento/product-community-edition

An insecure component vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. Magento 2 codebase leveraged outdated versions of JS libraries (Bootstrap, jquery, Knockout) with known security vulnerabilities.

Withdrawn: GHSA-6r5x-hmgg-7h53 — Remote code execution in Handlebars.js

2019-12-20T02:08:50+00:00

Withdrawn by the publisher.

Affected: npm: handlebars

Handlebars.js before 4.1.0 has Remote Code Execution (RCE)

GHSA-m5ff-3wj3-8ph4 — HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress

2019-12-26T16:34:06+00:00

Affected: PyPI: waitress

### Impact

If a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling.

``` Content-Length: 10 Transfer-Encoding: [\x0b]chunked ```

For clarity:

``` 0x0b == vertical tab ```

Would get parsed by Waitress as being a `chunked` request, but a front-end server would use the `Content-Length` instead as the `Transfer-Encoding` header is considered invalid due to containing invalid characters.

If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure.

### Patches

Please upgrade to Waitress 1.4.1 which fixes this issue with stricter HTTP field validation.

Waitress 1.4.1 due to this change has become much more strict in what is allowed in header values, while the maintainers don't believe that these changes will cause any issues, it may cause failures with non-conformist reverse proxies or clients, and it is highly recommend that users validate the changes in their environment and make sure it won't cause any unacceptable failures.

### Workarounds

You may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request.

Waitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection…

GHSA-f884-gm86-cg3q — PrestaShop module ps_facetedsearch might be vulnerable from CVE-2017-9841

2020-01-07T17:20:13+00:00

Affected: Packagist: prestashop/ps_facetedsearch

### Impact

We have identified that some ps_facetedsearch module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.

This vulnerability impacts - phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841) - phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)

### Patches

In the [security patch](https://github.com/PrestaShop/ps_facetedsearch/releases/tag/v3.4.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.

### Workarounds Users can also simply remove the unwanted vendor/phpunit folder.

### References https://nvd.nist.gov/vuln/detail/CVE-2017-9841

### For more information If you have any questions or comments about this advisory, email us at security@prestashop.com

GHSA-wqq8-mqj9-697f — PrestaShop autoupgrade module ZIP archives were vulnerable from CVE-2017-9841

2020-01-08T03:06:57+00:00

Affected: Packagist: prestashop/autoupgrade

### Impact

We have identified that some autoupgrade module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.

You can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).

### Patches

In the [security patch](https://github.com/PrestaShop/autoupgrade/releases/tag/v4.10.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.

### Workarounds Users can also simply remove the unwanted vendor/phpunit folder.

### References https://nvd.nist.gov/vuln/detail/CVE-2017-9841

### For more information If you have any questions or comments about this advisory, email us at security@prestashop.com

GHSA-769f-539v-f5jg — PrestaShop gamification module ZIP archives were vulnerable from CVE-2017-9841

2020-01-08T03:10:06+00:00

Affected: Packagist: prestashop/gamification

### Impact

We have identified that some gamification module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.

You can read PrestaShop official statement about this vulnerability [here](https://build.prestashop.com/news/critical-security-vulnerability-in-prestashop-modules/).

### Patches

In the [security patch](https://github.com/PrestaShop/gamification/releases/tag/v2.3.2), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.

### Workarounds Users can also simply remove the unwanted vendor/phpunit folder.

### References https://nvd.nist.gov/vuln/detail/CVE-2017-9841

### For more information If you have any questions or comments about this advisory, email us at security@prestashop.com

GHSA-9r27-994c-4xch — discord-html not escaping HTML code blocks when lacking a language identifier

2020-02-21T20:20:53+00:00

Affected: npm: discord-markdown

### Impact Any website using discord-markdown with user-generated markdown is vulnerable to having code injected into the page where the markdown is displayed.

### Patches This has been patched in version 2.3.1

### Workarounds Escape the characters `<>&` before sending plain code blocks to discord-markdown.

### References https://github.com/brussell98/discord-markdown/issues/13

GHSA-p94w-42g3-f7h4 — Holder can (re)create authentic credentials after receiving a credential in vp-toolkit

2020-02-28T16:38:09+00:00

Affected: npm: vp-toolkit

### Impact The [`verifyVerifiableCredential()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-credential-signer.ts#L57) method check the cryptographic integrity of the Verifiable Credential, but it does not check if the [`credential.issuer`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L129) DID matches the signer of the credential.

The **verifier** is impacted by this vulnerability.

### Patches Patch will be available in version 0.2.2.

### Workarounds In case you trust certain issuers for certain credentials as a verifier, trust the issuer's public key from the `credential.proof.verificationMethod` field.

### References [Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)

### For more information If you have any questions or comments about this advisory: * Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13) * [Contact me](https://github.com/rabomarnix)

GHSA-ff5x-w9wg-h275 — Holder can generate proof of ownership for credentials it does not control in vp-toolkit

2020-02-28T16:38:18+00:00

Affected: npm: vp-toolkit

### Impact The [`verifyVerifiablePresentation()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-presentation-signer.ts#L97) method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the [`credentialSubject.id`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L150) DID matches the signer of the VP proof.

The **verifier** is impacted by this vulnerability.

### Patches Patch will be available in version 0.2.2.

### Workarounds - Compute the address out of the `verifiablePresentation.proof.n.verificationMethod` using `getAddressFromPubKey()` from `crypt-util@0.1.5` and match it with the `credentialSubject.id` address from the credential.

### References [Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/14)

GHSA-738m-f33v-qc2r — SMTP Injection in PHPMailer

2020-03-05T21:57:18+00:00

Affected: Packagist: phpmailer/phpmailer

### Impact Attackers could inject arbitrary SMTP commands via by exploiting the fact that valid email addresses may contain line breaks, which are not handled correctly in some contexts.

### Patches Fixed in 5.2.14 in [this commit](https://github.com/PHPMailer/PHPMailer/commit/6687a96a18b8f12148881e4ddde795ae477284b0).

### Workarounds Manually strip line breaks from email addresses before passing them to PHPMailer.

### References https://nvd.nist.gov/vuln/detail/CVE-2015-8476

### For more information If you have any questions or comments about this advisory: * Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)