ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
Packagist
|
GHSA-7v3x-h7r2-34jv
|
Insufficient Session Expiration in Pterodactyl API
|
### Impact
A vulnerability exists in Pterodactyl Panel `<= 1.6.6` that could allow a malicious attacker that compromises an API key to generate an authenticated user session that is not revoked when the API key is deleted, thus allowing the malicious user to remain logged in as the user the key belonged to.
It is important to note that **a malicious user must first compromise an existing API key for a user to exploit this issue**. It cannot be exploited by chance, and requires a coordinated attack against an individual account using a known API key.
### Patches
This issue has been addressed in the `v1.7.0` release of Pterodactyl Panel.
### Workarounds
Those not wishing to upgrade may apply the change below:
```diff
diff --git a/app/Http/Middleware/Api/AuthenticateKey.php b/app/Http/Middleware/Api/AuthenticateKey.php
index eb25dac6..857bfab2 100644
--- a/app/Http/Middleware/Api/AuthenticateKey.php
+++ b/app/Http/Middleware/Api/AuthenticateKey.php
@@ -70,7 +70,7 @@ class AuthenticateKey
} else {
$model = $this->authenticateApiKey($request->bearerToken(), $keyType);
- $this->auth->guard()->loginUsingId($model->user_id);
+ $this->auth->guard()->onceUsingId($model->user_id);
}
```
### For more information
If you have any questions or comments about this advisory please reach out to `Tactical Fish#8008` on [Discord](https://discord.gg/pterodactyl) or email `dane@pterodactyl.io`.
| null |
2022-01-20T16:18:28Z
|
2022-01-21T18:43:05Z
|
MODERATE
| null |
{'CWE-613'}
|
{'https://github.com/pterodactyl/panel/security/advisories/GHSA-7v3x-h7r2-34jv', 'https://github.com/pterodactyl/panel', 'https://github.com/pterodactyl/panel/releases/tag/v1.7.0', 'https://github.com/pterodactyl/panel/commit/dfa329ddf242908b60e22e3340ea36359eab1ef4'}
| null |
Packagist
|
GHSA-6pj2-5fqq-xvjc
|
Incorrect Authorization in latte/latte
|
This affects the package latte/latte before 2.10.6. There is a way to bypass allowFunctions that will affect the security of the application. When the template is set to allow/disallow the use of certain functions, adding control characters (x00-x08) after the function will bypass these restrictions.
|
{'CVE-2021-23803'}
|
2022-01-06T18:54:41Z
|
2022-01-06T20:56:27Z
|
CRITICAL
| null |
{'CWE-863'}
|
{'https://github.com/nette/latte/issues/279', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23803', 'https://snyk.io/vuln/SNYK-PHP-LATTELATTE-1932226', 'https://github.com/nette/latte/commit/227c86eda9a8a6d060ea8501923e768b6d992210', 'https://github.com/nette/latte'}
| null |
Packagist
|
GHSA-pjjf-hc4q-g298
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF)
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF).
|
{'CVE-2021-3775'}
|
2021-11-17T21:11:29Z
|
2021-11-15T23:16:17Z
|
MODERATE
| null |
{'CWE-352'}
|
{'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351', 'https://huntr.dev/bounties/6a59d203-4ca7-4aed-bdb9-1e39b66c77b3', 'https://github.com/star7th/showdoc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3775'}
| null |
Packagist
|
GHSA-8m28-w6xg-35hw
|
Cross-Site Request Forgery (CSRF) in livehelperchat
|
livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)
|
{'CVE-2022-0231'}
|
2022-01-24T22:54:21Z
|
2022-01-26T20:22:08Z
|
MODERATE
| null |
{'CWE-352'}
|
{'https://github.com/livehelperchat/livehelperchat/commit/6ad1349dc5e7503b00c5017499a0a895d7654a61', 'https://huntr.dev/bounties/adaf98cf-60ab-40e0-aa3b-42ba0d3b7cbf', 'https://github.com/livehelperchat/livehelperchat', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0231'}
| null |
Packagist
|
GHSA-72hm-fx78-xwhc
|
XSS vulnerability on contacts view
|
### Impact
Mautic versions before 3.3.4/4.0.0 are vulnerable to an inline JS XSS attack through the contact's first or last name and triggered when viewing a contact's details page then clicking on the action drop down and hovering over the Campaigns button. Contact first and last name can be populated from different sources such as UI, API, 3rd party syncing, forms, etc.
### Patches
Upgrade to 3.3.4 or 4.0.0
### Workarounds
No
### References
https://github.com/mautic/mautic/releases/tag/3.3.4
https://github.com/mautic/mautic/releases/tag/4.0.0
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org)
|
{'CVE-2021-27911'}
|
2021-08-30T18:05:52Z
|
2021-09-01T18:40:40Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/mautic/mautic/security/advisories/GHSA-72hm-fx78-xwhc', 'https://github.com/mautic/mautic', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27911'}
| null |
Packagist
|
GHSA-gp2m-7cfp-h6gf
|
Incorrect persistent NameID generation in SimpleSAMLphp
|
### Background
When a SimpleSAMLphp Identity Provider is misconfigured, a bug in the software when trying to build a persistent `NameID` to univocally identify the authenticating subject could cause different users to get the same identifier generated, depending on the attributes available for them right after authentication.
Please note that even though this is possible thanks to a bug, **an IdP must be misconfigured** to release persistent `NameID`s even if it is not properly configured to generate them based on the specifics of the deployment.
### Description
Persistent `NameID`s will typically be sent as part of the `Subject` element of a SAML assertion, or as the contents of the `eduPersonTargetedID` attribute. Here is an example of such a `NameID`:
<NameID Format=“urn:oasis:names:tc:SAML:2.0:nameid-format:persistent“>
zbonsm0Yn9Gnw14uQEEPr6AO7d+IvxwCQN3t+o24jYs=
</NameID>
Some service providers will use this information to identify a user across sessions because a persistent `NameID` will never change for a given user. This could lead to different users accessing the same account in those service providers.
In order to be affected by this issue, the following circumstances must concur:
- SimpleSAMLphp acts as an identity provider.
- The service provider asking for authentication requests a persistent `NameID`.
- No `saml:PersistentNameID` authentication processing filter is configured (neither for the whole IdP, nor for a given SP).
- No `simplesaml.nameidattribute` configuration option is set (neither for the whole IdP, nor for a given SP).
- One of the following alternatives:
- No `userid.attribute` configuration option is set **and** the users don't have an `eduPersonPrincipalName` attribute in the users backend, **or**
- the `userid.attribute` configuration option is set to an empty or missing attribute.
If all these requirements are met, the `SimpleSAML_Auth_ProcessingChain` class will try to keep a unique user identifier in the state array (`addUserID()` method). Bear in mind that this code is executed **before** all the authentication processing filters configured, meaning that only those attributes retrieved for the user during **initial authentication** will be available. If no `userid.attribute` configuration option is set, the default `eduPersonPrincipalName` will then be used. However, since it is missing, no identifier will be kept. Alternatively, if `userid.attribute` is set to a missing or empty attribute, the `addUserID()` method will abort trying to register an identifier.
After executing all authentication processing filters, SimpleSAMLphp will build a SAML assertion. If the service provider requests persistent `NameID`s, SimpleSAMLphp will attempt to generate one given that none is already available (because the `saml:PersistentNameID` filter was not used). At this point, the code will look for the `simplesaml.nameidattribute` configuration option in either the local IdP metadata or in the remote SP metadata. If none of them are configured, it will default to the unique user identifier previously registered by `SimpleSAML_Auth_ProcessingChain`. If no identifier was kept there, the code will log an error message:
Unable to generate NameID. Check the userid.attribute option.
However, instead of aborting the `NameID` generation at that point, it will go on and use a value missing from the state array as the source for the computation, meaning the `null` type will be used. Hence, all users connecting to a given service provider will get the same `NameID` generated, because all the input parameters will be the same:
- The SP's entity identifier.
- The IdP's entity identifier.
- The `null` value.
- The common secret salt from the main configuration.
### Affected versions
All SimpleSAMLphp versions between 1.7.0 and 1.14.10, inclusive.
### Impact
Those identity providers affected by this bug and misconfigured as previously described could be issuing SAML assertions with common `NameID`s for all or a subset of their users. If a service provider uses those `NameID`s to identify the users of the affected IdP, all the users will be associated with the same user account at the service provider, causing all sorts of potential security issues like information disclosure or unauthorized access.
While we can consider this unlikely to happen, some cases have been already observed. In particular, some identity providers using default configurations and consuming metadata automatically (i.e. using the _metarefresh_ module) while using a user backend like _Active Directory_ that does not populate `eduPersonPrincipalName` are particularly sensitive to this issue.
### Resolution
Upgrade to the latest version.
Configure a `saml:PersistentNameID` authentication processing filter according to your needs. Remember to check that **the attribute used as the source** for the `NameID` **is present at the moment the `saml:PersistentNameID` filter is executed**. The attribute used must be **unique** per user, and **must not change** over time.
|
{'CVE-2017-12873'}
|
2021-08-19T16:44:17Z
|
2020-01-24T21:28:06Z
|
CRITICAL
| null |
{'CWE-384'}
|
{'https://www.debian.org/security/2018/dsa-4127', 'https://github.com/simplesamlphp/simplesamlphp/security/advisories/GHSA-gp2m-7cfp-h6gf', 'https://lists.debian.org/debian-lts-announce/2017/12/msg00007.html', 'https://simplesamlphp.org/security/201612-04', 'https://github.com/simplesamlphp/simplesamlphp/commit/90dca835158495b173808273e7df127303b8b953', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12873'}
| null |
Packagist
|
GHSA-9jp8-cwwx-p64q
|
XSS in richtext custom tag attributes in ezsystems/ezplatform-richtext
|
The rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.
| null |
2021-11-29T20:55:01Z
|
2021-12-01T18:28:38Z
|
MODERATE
| null | null |
{'https://github.com/ezsystems/ezplatform-admin-ui/security/advisories/GHSA-9jp8-cwwx-p64q', 'https://developers.ibexa.co/security-advisories/ibexa-sa-2021-010-xss-in-richtext-custom-tag-attributes', 'https://github.com/ezsystems/ezplatform-admin-ui/'}
| null |
Packagist
|
GHSA-cq58-r77c-5jjw
|
Cross-site scripting (XSS) from image block content in the site frontend
|
### Impact
Kirby's [blocks field](https://getkirby.com/docs/reference/panel/fields/blocks) stores structured data for each block. This data is then used in [block snippets](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) to convert the blocks to HTML for use in your templates. We recommend to [escape HTML special characters](https://getkirby.com/docs/guide/templates/escaping) against cross-site scripting (XSS) attacks.
Cross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.
The default snippet for the [image block](https://getkirby.com/docs/reference/panel/blocks/image) unfortunately did not use our escaping helper. This made it possible to include malicious HTML code in the source, alt and link fields of the image block, which would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.
This vulnerability is critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.
You are *not* affected if you don't use the blocks field or specifically the image block in any of your blueprints. You are also protected if you use a custom [block snippet](https://getkirby.com/docs/reference/panel/fields/blocks#block-snippets) that either escapes the printed values or doesn't use them. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into the image block content.
### Patches
We have patched the vulnerability in [Kirby 3.5.8](https://github.com/getkirby/kirby/releases/tag/3.5.8) by escaping special HTML characters in the output from the default image block snippet. Please update to this or a [later version](https://github.com/getkirby/kirby/releases/) to fix the vulnerability.
### Credits
Thanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.
|
{'CVE-2021-41258'}
|
2021-11-16T15:49:36Z
|
2021-11-16T17:04:41Z
|
MODERATE
| null |
{'CWE-79', 'CWE-80'}
|
{'https://github.com/getkirby/kirby/pull/3510', 'https://github.com/getkirby/kirby/security/advisories/GHSA-cq58-r77c-5jjw', 'https://github.com/getkirby/kirby/releases/tag/3.5.8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41258', 'https://github.com/getkirby/kirby'}
| null |
Packagist
|
GHSA-4j77-gg36-9864
|
Cross-Site Scripting in TYPO3 CMS Link Handling
|
It has been discovered that link tags generated by `typolink` functionality are vulnerable to cross-site scripting - properties being assigned as HTML attributes have not been parsed correctly.
Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.
### References
* https://typo3.org/security/advisory/typo3-core-sa-2020-003
|
{'CVE-2020-11065'}
|
2021-01-08T20:17:04Z
|
2020-05-13T23:18:12Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-4j77-gg36-9864', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11065'}
| null |
Packagist
|
GHSA-qwmj-72mp-q3m2
|
Missing Authorization in TYPO3 extension
|
The direct_mail extension through 5.2.3 for TYPO3 allows Information Disclosure via a newsletter subscriber data Special Query.
|
{'CVE-2020-12700'}
|
2021-07-28T19:17:48Z
|
2021-07-26T21:34:58Z
|
MODERATE
| null |
{'CWE-862'}
|
{'https://typo3.org/help/security-advisories', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12700', 'https://typo3.org/security/advisory/typo3-ext-sa-2020-005'}
| null |
Packagist
|
GHSA-5875-p652-2ppm
|
Exposure of Resource to Wrong Sphere in microweber
|
Exposure of Resource to Wrong Sphere in microweber prior to 1.3 allows users to add deleted products to a cart and buy it.
|
{'CVE-2022-0762'}
|
2022-03-09T20:31:39Z
|
2022-02-27T00:00:16Z
|
MODERATE
| null |
{'CWE-668'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0762', 'https://huntr.dev/bounties/125b5244-5099-485e-bf75-e5f1ed80dd48', 'https://github.com/microweber/microweber/commit/76361264d9fdfff38a1af79c63141455cc4d36e3'}
| null |
Packagist
|
GHSA-5x33-h32w-6vr2
|
Cross site-scripting (XSS) moodle
|
The filter in the tag manager required extra sanitizing to prevent a reflected XSS risk. This affects 3.9 to 3.9.1, 3.8 to 3.8.4, 3.7 to 3.7.7, 3.5 to 3.5.13 and earlier unsupported versions. Fixed in 3.9.2, 3.8.5, 3.7.8 and 3.5.14.
|
{'CVE-2020-25628'}
|
2021-03-24T23:14:52Z
|
2021-03-29T20:43:15Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/moodle/moodle/commit/e8632a4ad0b4da3763cbbe5949594aa449b483bb', 'http://git.moodle.org/gw?p=moodle.git&a=search&h=HEAD&st=commit&s=MDL-69340', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25628', 'https://moodle.org/mod/forum/discuss.php?d=410840'}
| null |
Packagist
|
GHSA-vgwr-773q-7j3c
|
Path Traversal within joomla/archive zip class
|
An issue was discovered in Joomla! 3.0.0 through 3.9.24. Extracting an specifilcy crafted zip package could write files outside of the intended path.
|
{'CVE-2021-26028'}
|
2021-03-24T17:57:48Z
|
2021-03-24T17:58:13Z
|
MODERATE
| null |
{'CWE-22'}
|
{'https://github.com/joomla-framework/archive/commit/32c9009a1020d16bc1060c0d06339898b697cf2c', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/joomla/archive/CVE-2021-26028.yaml', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26028', 'https://developer.joomla.org/security-centre/848-20210308-core-path-traversal-within-joomla-archive-zip-class.html'}
| null |
Packagist
|
GHSA-mmjr-5q74-p3m4
|
Exposure of Resource to Wrong Sphere in Drupal Core
|
Information Disclosure vulnerability in file module of Drupal Core allows an attacker to gain access to the file metadata of a permanent private file that they do not have access to by guessing the ID of the file. This issue affects: Drupal Core 8.8.x versions prior to 8.8.10; 8.9.x versions prior to 8.9.6; 9.0.x versions prior to 9.0.6.
|
{'CVE-2020-13670'}
|
2022-02-25T15:35:08Z
|
2022-02-12T00:00:47Z
|
HIGH
| null |
{'CWE-668'}
|
{'https://github.com/drupal/core', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13670', 'https://www.drupal.org/sa-core-2020-011'}
| null |
Packagist
|
GHSA-vvwv-h69m-wg6f
|
XXE in PHPSpreadsheet due to incomplete fix for previous encoding issue
|
PHPOffice PhpSpreadsheet before 1.8.0 has an XXE issue. The XmlScanner decodes the sheet1.xml from an .xlsx to utf-8 if something else than UTF-8 is declared in the header. This was a security measurement to prevent CVE-2018-19277 but the fix is not sufficient. By double-encoding the the xml payload to utf-7 it is possible to bypass the check for the string ?<!ENTITY? and thus allowing for an xml external entity processing (XXE) attack.
|
{'CVE-2019-12331'}
|
2021-08-18T22:44:15Z
|
2019-11-20T01:39:57Z
|
HIGH
| null |
{'CWE-611'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-12331', 'https://github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.8.0', 'https://herolab.usd.de/security-advisories/usd-2019-0046/', 'https://github.com/PHPOffice/PhpSpreadsheet/blob/master/CHANGELOG.md#180---2019-07-01'}
| null |
Packagist
|
GHSA-56cx-wf47-hx7w
|
Improper Restriction of Excessive Authentication Attempts
|
firefly-iii is vulnerable to Improper Restriction of Excessive Authentication Attempts
|
{'CVE-2021-3663'}
|
2021-08-31T20:58:20Z
|
2021-08-09T20:38:37Z
|
MODERATE
| null |
{'CWE-307'}
|
{'https://huntr.dev/bounties/497bdf6d-7dba-49c3-8011-1c64dfbb3380', 'https://github.com/firefly-iii/firefly-iii/releases/tag/5.5.13', 'https://github.com/firefly-iii/firefly-iii/commit/afc9f4b7ebc8a240c85864a6e1abda62bfeefae8', 'https://github.com/firefly-iii/firefly-iii', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3663'}
| null |
Packagist
|
GHSA-p4pj-9g59-4ppv
|
Remote Code Execution in SyliusResourceBundle
|
### Impact
Request parameters injected inside an expression evaluated by `symfony/expression-language` package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.
The vulnerable versions include: `<=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3`.
### Example
```yaml
foo:
path: /foo/{id}
defaults:
_sylius:
repository:
method: findSome
arguments:
entity: "expr:service('repository').find($id)"
```
In this case, `$id` can be prepared in a way that calls other services.
If you visit `/foo/"~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~"`, it will result in a following expression `expr:service('repository').find(""~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~"")`, which will execute a query on the currently connected database.
To find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.
### Patches
This issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.
### Workarounds
The fix requires adding `addslashes` in `ParametersParser::parseRequestValueExpression` to sanitize user input before evaluating it using the expression language.
```php
- return is_string($variable) ? sprintf('"%s"', $variable) : $variable;
+ return is_string($variable) ? sprintf('"%s"', addslashes($variable)) : $variable;
```
### Acknowledgements
This security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@sylius.com](mailto:security@sylius.com)
|
{'CVE-2020-15143'}
|
2021-11-19T15:41:13Z
|
2020-08-19T21:04:25Z
|
HIGH
| null |
{'CWE-917', 'CWE-74'}
|
{'https://github.com/Sylius/SyliusResourceBundle', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15143', 'https://github.com/Sylius/SyliusResourceBundle/security/advisories/GHSA-p4pj-9g59-4ppv'}
| null |
Packagist
|
GHSA-wv23-pfj7-2mjj
|
Authenticated file write leads to remote code execution in october/system
|
### Impact
Assuming an attacker with "create, modify and delete website pages" privileges in the backend is able to execute PHP code by running specially crafted Twig code in the template markup.
### Patches
Issue has been patched in Build 473 and v1.1.6
### Workarounds
Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.
### References
Credits to:
• David Miller
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
|
{'CVE-2021-32649'}
|
2022-01-26T22:27:50Z
|
2022-01-14T21:08:23Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://github.com/octobercms/october', 'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26', 'https://github.com/octobercms/october/security/advisories/GHSA-wv23-pfj7-2mjj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32649'}
| null |
Packagist
|
GHSA-mcx4-f5f5-4859
|
Prevent cache poisoning via a Response Content-Type header in Symfony
|
Description
-----------
When a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.
Resolution
----------
Symfony does not use the `Accept` header anymore to guess the `Content-Type`.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6) for the 4.4 branch.
Credits
-------
I would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.
|
{'CVE-2020-5255'}
|
2021-01-08T20:25:26Z
|
2020-03-30T20:09:16Z
|
LOW
| null |
{'CWE-435'}
|
{'https://github.com/symfony/symfony/security/advisories/GHSA-mcx4-f5f5-4859', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5255', 'https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6', 'https://symfony.com/blog/cve-2020-5255-prevent-cache-poisoning-via-a-response-content-type-header', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36JLPHUPKDFAX6D5WYFC4ALO2K7RDUQ/'}
| null |
Packagist
|
GHSA-prg5-hg25-8grq
|
Ability to switch channels via GET parameter enabled in production environments
|
### Impact
This vulnerability gives the ability to switch channels via the `_channel_code` GET parameter in production environments. This was meant to be enabled only when `%kernel.debug%` is set to true.
However, if no `sylius_channel.debug` is set explicitly in the configuration, the default value which is `%kernel.debug%` will be not resolved and cast to boolean, enabling this debug feature even if that parameter is set to false.
### Patches
Patch has been provided for Sylius 1.3.x and newer - **1.3.16, 1.4.12, 1.5.9, 1.6.5**. Versions older than 1.3 are not covered by our security support anymore.
### Workarounds
Unsupported versions could be patched by adding the following configuration to run in production:
```yaml
sylius_channel:
debug: false
```
|
{'CVE-2020-5218'}
|
2021-01-08T20:32:23Z
|
2020-01-31T18:00:58Z
|
LOW
| null |
{'CWE-444'}
|
{'https://github.com/Sylius/Sylius/security/advisories/GHSA-prg5-hg25-8grq', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/sylius/resource-bundle/CVE-2020-5220.yaml', 'https://github.com/Sylius/SyliusResourceBundle/security/advisories/GHSA-8vp7-j5cj-vvm2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5218'}
| null |
Packagist
|
GHSA-43f8-p5w3-5m25
|
SSRF by connecting to privileged ports
|
### Impact
All users are affected.
### Patches
* Unsuccessfully patched by 0fae40fb, included in version [4.4.0](https://github.com/vrana/adminer/releases/tag/v4.4.0).
* Patched by 35bfaa75, included in version [4.7.8](https://github.com/vrana/adminer/releases/tag/v4.7.8).
### Workarounds
Protect access to Adminer also by other means, e.g. by HTTP password, IP address limiting or by OTP [plugin](https://www.adminer.org/plugins/).
### References
* http://hyp3rlinx.altervista.org/advisories/ADMINER-UNAUTHENTICATED-SERVER-SIDE-REQUEST-FORGERY.txt
* https://sourceforge.net/p/adminer/bugs-and-features/769/
* https://gusralph.info/adminer-ssrf-bypass-cve-2018-7667/ (CVE-2020-28654)
### For more information
If you have any questions or comments about this advisory:
* Comment at 35bfaa75.
|
{'CVE-2018-7667'}
|
2021-02-22T20:42:46Z
|
2021-02-11T21:20:40Z
|
MODERATE
| null |
{'CWE-918'}
|
{'https://packagist.org/packages/vrana/adminer', 'https://sourceforge.net/p/adminer/bugs-and-features/769/', 'https://gusralph.info/adminer-ssrf-bypass-cve-2018-7667', 'http://hyp3rlinx.altervista.org/advisories/ADMINER-UNAUTHENTICATED-SERVER-SIDE-REQUEST-FORGERY.txt', 'https://github.com/vrana/adminer/security/advisories/GHSA-43f8-p5w3-5m25'}
| null |
Packagist
|
GHSA-9fcc-7g44-mxrj
|
Cross-site Scripting in ShowDoc
|
ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via uploading files with files in `.xsd`, `.asa`, and `.aspx` formats.
|
{'CVE-2022-0942'}
|
2022-03-29T17:30:52Z
|
2022-03-16T00:00:47Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/star7th/showdoc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0942', 'https://huntr.dev/bounties/a412707c-18da-4c84-adc0-9801ed8068c9', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'}
| null |
Packagist
|
GHSA-g8jx-66p8-vcm2
|
SQL injection in pimcore/pimcore
|
This affects the package pimcore/pimcore before 10.0.7. This issue exists due to the absence of check on the storeId parameter in the method collectionsActionGet and groupsActionGet method within the ClassificationstoreController class.
|
{'CVE-2021-23405'}
|
2021-07-28T17:37:01Z
|
2021-07-13T17:42:31Z
|
HIGH
| null |
{'CWE-89'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23405', 'https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-1316297', 'https://github.com/pimcore/pimcore/pull/9572'}
| null |
Packagist
|
GHSA-m434-m5pv-p35w
|
Insufficient user authorization in Moodle
|
A flaw was found in Moodle in versions 3.11 to 3.11.4, 3.10 to 3.10.8, 3.9 to 3.9.11 and earlier unsupported versions. The calendar:manageentries capability allowed managers to access or modify any calendar event, but should have been restricted from accessing user level events.
|
{'CVE-2022-0333'}
|
2022-02-02T16:12:13Z
|
2022-01-28T22:08:02Z
|
LOW
| null |
{'CWE-863'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0333', 'https://github.com/moodle/moodle', 'https://bugzilla.redhat.com/show_bug.cgi?id=2043663', 'https://moodle.org/mod/forum/discuss.php?d=431100', 'https://github.com/moodle/moodle/commit/2ee27313cea0d7073f5a6a35eccdfddcb3a9adad'}
| null |
Packagist
|
GHSA-q9cp-mc96-m4w2
|
XML External Entity in Dashboard Widget
|
### Problem
It has been discovered that RSS widgets are susceptible to XML external entity processing.
This vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions.
At least with _libxml2_ version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed.
### Solution
Update to TYPO3 version 10.4.10 that fixes the problem described.
|
{'CVE-2020-26229'}
|
2021-01-07T22:39:29Z
|
2020-11-23T21:18:44Z
|
LOW
| null |
{'CWE-611'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-26229', 'https://typo3.org/security/advisory/typo3-core-sa-2020-012', 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-q9cp-mc96-m4w2'}
| null |
Packagist
|
GHSA-jm6p-wfjg-xm7x
|
bookstack is vulnerable to Improper Access Control
|
bookstack is vulnerable to Improper Access Control.
|
{'CVE-2021-4026'}
|
2021-12-02T15:29:37Z
|
2021-12-01T18:26:48Z
|
MODERATE
| null |
{'CWE-668', 'CWE-284'}
|
{'https://huntr.dev/bounties/c6dfa80d-43e6-4b49-95af-cc031bb66b1d', 'https://github.com/BookStackApp/BookStack/releases/tag/v21.11.2', 'https://github.com/bookstackapp/bookstack/', 'https://github.com/bookstackapp/bookstack/commit/b4fa82e3298a15443ca40bff205b7a16a1031d92', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4026'}
| null |
Packagist
|
GHSA-5cmw-fhq9-8fhh
|
Type Confusion in LiveHelperChat
|
Live Helper Chat provides live support for your website. Loose comparison causes IDOR on multiple endpoints in LiveHelperChat prior to 3.96. There is a fix released in versions 3.96 and 3.97. Currently, there is no known workaround.
|
{'CVE-2022-1176'}
|
2022-04-12T18:10:00Z
|
2022-04-01T00:00:40Z
|
HIGH
| null |
{'CWE-843'}
|
{'https://github.com/livehelperchat/livehelperchat/commit/72c0df160bfe9838c618652facef29af99392ce3', 'https://huntr.dev/bounties/3e30171b-c9bf-415c-82f1-6f55a44d09d3', 'https://github.com/livehelperchat/livehelperchat', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1176'}
| null |
Packagist
|
GHSA-j6jg-w79c-7p8v
|
File Upload Restriction Bypass leading to Cross-site Scripting in ShowDoc
|
ShowDoc prior to 2.10.4 is vulnerable to a file upload restriction bypass leading to stored cross-site scripting.
|
{'CVE-2022-0951'}
|
2022-03-28T19:36:26Z
|
2022-03-16T00:00:48Z
|
MODERATE
| null |
{'CWE-79', 'CWE-434'}
|
{'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3', 'https://huntr.dev/bounties/b3a983a3-17f9-4aa8-92d7-8a0c92a93932', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0951', 'https://github.com/star7th/showdoc'}
| null |
Packagist
|
GHSA-8xx9-rxrj-2m2w
|
Cross-site Scripting in pimcore
|
pimcore is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
|
{'CVE-2021-4139'}
|
2022-01-04T21:18:40Z
|
2022-01-05T20:35:12Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/pimcore/pimcore', 'https://github.com/pimcore/pimcore/commit/d5c3e876d910784000335061c3bd24d301351245', 'https://huntr.dev/bounties/6ec59e43-095f-4ba3-8b75-e92250da8e3a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4139'}
| null |
Packagist
|
GHSA-94vp-rmqv-5875
|
Twig Sandbox Escape by authenticated users with access to editing CMS templates when safemode is enabled.
|
### Impact
An authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.
This is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.
### Patches
Issue has been patched in Build 469 (v1.0.469) and v1.1.0.
### Workarounds
Apply https://github.com/octobercms/october/compare/106daa2930de4cebb18732732d47d4056f01dd5b...7cb148c1677373ac30ccfd3069d18098e403e1ca to your installation manually if unable to upgrade to Build 469.
### References
Reported by [ka1n4t](https://github.com/ka1n4t)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1108" alt="Screen Shot 2020-10-10 at 1 21 13 PM" src="https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png">
|
{'CVE-2020-15247'}
|
2021-11-19T13:42:37Z
|
2020-11-23T19:48:27Z
|
MODERATE
| null |
{'CWE-862'}
|
{'https://github.com/octobercms/october', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15247', 'https://github.com/octobercms/october/security/advisories/GHSA-94vp-rmqv-5875', 'https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982'}
| null |
Packagist
|
GHSA-8mq9-fqv8-59wf
|
Cross-Site Scripting in Page Preview
|
> ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.0)
### Problem
Failing to properly encode _Page TSconfig_ settings, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
### Solution
Update to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described.
### Credits
Thanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.
### References
* [TYPO3-CORE-SA-2021-009](https://typo3.org/security/advisory/typo3-core-sa-2021-009)
|
{'CVE-2021-32667'}
|
2021-08-31T21:22:31Z
|
2021-07-22T19:34:43Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-8mq9-fqv8-59wf', 'https://typo3.org/security/advisory/typo3-core-sa-2021-009', 'https://github.com/TYPO3/typo3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32667', 'https://github.com/TYPO3/typo3/security/advisories/GHSA-8mq9-fqv8-59wf'}
| null |
Packagist
|
GHSA-8jq6-w5cg-wm45
|
Exploitable inventory component chaining in PocketMine-MP
|
### Impact
Specially crafted `InventoryTransactionPacket`s sent by malicious clients were able to exploit the behaviour of `InventoryTransaction->findResultItem()` and cause it to take an abnormally long time to execute (causing an apparent server freeze).
The affected code is intended to compact conflicting `InventoryActions` which are in the same `InventoryTransaction` by flattening them into a single action. When multiple pathways to a result existed, the complexity of this flattening became exponential.
The problem was fixed by bailing when ambiguities are detected.
**At the time of writing, this exploit is being used in the wild by attackers to deny service to servers.**
### Patches
Upgrade to 3.15.4 or newer.
### Workarounds
No practical workarounds are possible, short of backporting the fix or implementing checks in a plugin listening to `DataPacketReceiveEvent`.
### References
c368ebb5e74632bc622534b37cd1447b97281e20
### For more information
If you have any questions or comments about this advisory:
* Email us at [team@pmmp.io](mailto:team@pmmp.io)
| null |
2020-11-11T21:38:07Z
|
2020-11-11T21:38:18Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-8jq6-w5cg-wm45'}
| null |
Packagist
|
GHSA-c65v-p733-9796
|
Cross-site Scripting in snipe/snipe-it
|
snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
|
{'CVE-2021-3961'}
|
2021-11-22T18:39:54Z
|
2021-11-23T18:17:33Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/snipe/snipe-it/commit/7ce5993f5ae9d713a0955c2fd8e2dff7a7ce886e', 'https://huntr.dev/bounties/5987aed5-6613-4937-8a3e-d48009b7da10', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3961'}
| null |
Packagist
|
GHSA-6r58-4xgr-gm6m
|
Priviledge escalation through cache pollution
|
In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.
|
{'CVE-2019-12617'}
|
2019-11-12T22:50:54Z
|
2019-11-12T23:01:59Z
|
MODERATE
| null | null |
{'https://www.silverstripe.org/blog/tag/release', 'https://www.silverstripe.org/download/security-releases/', 'https://forum.silverstripe.org/c/releases', 'https://www.silverstripe.org/download/security-releases/CVE-2019-12617', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12617'}
| null |
Packagist
|
GHSA-rpxh-vg2x-526v
|
List of order ids, number, items total and token value exposed for unauthorized uses via new API
|
### Impact
Part of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time.
### Patches
The problem has been patched at Sylius 1.9.5 and 1.10.0
### Workarounds
There are a few ways to fix this without updating the code.
The first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:
```yaml
access_control:
# ...
- { path: "%sylius.security.new_api_shop_regex%/orders", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }
- { path: "%sylius.security.new_api_shop_regex%/orders", role: ROLE_USER, methods: [GET] }
```
This would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only.
The second possible solution is to decorate the `\Sylius\Bundle\ApiBundle\Doctrine\QueryCollectionExtension\OrdersByLoggedInUserExtension` and throw `Symfony\Component\Security\Core\Exception\AccessDeniedException` if the class is executed for unauthorized user.
|
{'CVE-2021-32720'}
|
2021-06-30T17:59:43Z
|
2021-06-29T03:12:04Z
|
MODERATE
| null |
{'CWE-200'}
|
{'https://packagist.org/packages/sylius/sylius', 'https://github.com/Sylius/Sylius/commit/21d509851559230d03292b2a635a6951748c2758', 'https://github.com/Sylius/Sylius/security/advisories/GHSA-rpxh-vg2x-526v', 'https://github.com/Sylius/Sylius/releases/tag/v1.9.5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32720'}
| null |
Packagist
|
GHSA-f8pv-x7h8-687v
|
Cross-site scripting in feehicms
|
Insufficient filtering of the tag parameters in feehicms 0.1.3 allows attackers to execute arbitrary web or HTML via a crafted payload.
|
{'CVE-2020-19709'}
|
2021-09-02T18:50:42Z
|
2021-08-30T16:22:25Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/liufee/feehicms', 'https://github.com/liufee/feehicms/issues/2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-19709'}
| null |
Packagist
|
GHSA-cv25-3gmg-c6m8
|
Injection in UserFrosting
|
In Userfrosting, versions v0.3.1 to v4.6.2 are vulnerable to Host Header Injection. By luring a victim application user to click on a link, an unauthenticated attacker can use the “forgot password” functionality to reset the victim’s password and successfully take over their account.
|
{'CVE-2021-25994'}
|
2022-01-14T19:42:47Z
|
2022-01-06T22:22:32Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25994', 'https://github.com/userfrosting/UserFrosting', 'https://github.com/userfrosting/UserFrosting/commit/796dd78757902435d1bd286415feea78098e45ba', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25994'}
| null |
Packagist
|
GHSA-674v-3g2w-84gx
|
Sandbox bypass in fenom
|
In fenom 2.12.1 and before, there is a way in fenom/src/Fenom/Template.php function getTemplateCode()to bypass sandbox to execute arbitrary PHP code when disable_native_funcs is true.
|
{'CVE-2021-46433'}
|
2022-04-05T18:52:09Z
|
2022-03-29T00:01:15Z
|
CRITICAL
| null | null |
{'https://github.com/fenom-template/fenom', 'https://github.com/fenom-template/fenom/issues/331', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46433'}
| null |
Packagist
|
GHSA-r6mv-ppjc-4hgr
|
PHP file inclusion via insert tags
|
### Impact
It is possible for untrusted users to load arbitrary PHP files via insert tags.
Installations are only affected if there are untrusted back end users.
### Patches
Update to Contao 4.4.56, 4.9.18 or 4.11.7.
### Workarounds
Disable the login for untrusted back end users.
### References
https://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags.html
### For more information
If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).
|
{'CVE-2021-37626'}
|
2021-08-23T16:51:34Z
|
2021-08-23T19:41:04Z
|
MODERATE
| null |
{'CWE-94'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-37626', 'https://github.com/contao/contao/security/advisories/GHSA-r6mv-ppjc-4hgr', 'https://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags.html'}
| null |
Packagist
|
GHSA-xm6j-x342-gwq9
|
Unpublished files are exposed publicly
|
In the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)
|
{'CVE-2019-16409'}
|
2021-07-27T22:02:46Z
|
2019-11-12T23:01:05Z
|
MODERATE
| null |
{'CWE-200'}
|
{'https://github.com/silverstripe/silverstripe-framework', 'https://github.com/symbiote/silverstripe-versionedfiles', 'https://www.silverstripe.org/download/security-releases/cve-2019-16409', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16409'}
| null |
Packagist
|
GHSA-rpw6-9xfx-jvcx
|
Directory Traversal in Archive_Tar
|
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
:exclamation: Note: There was an [initial fix](https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916) for this vulnerability made in version `1.4.12`. That fix introduced a bug which was [fixed in 1.4.13](https://github.com/pear/Archive_Tar/pull/36). Therefore we have set the first-patched-version to `1.4.13` which the earliest working version that avoids this vulnerability.
|
{'CVE-2020-36193'}
|
2021-09-20T20:27:34Z
|
2021-04-22T16:20:36Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/FriendsOfPHP/security-advisories/blob/master/pear/archive_tar/CVE-2020-36193.yaml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36193', 'https://lists.debian.org/debian-lts-announce/2021/04/msg00007.html', 'https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42GPGVVFTLJYAKRI75IVB5R45NYQGEUR/', 'https://www.debian.org/security/2021/dsa-4894', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FOZNK4FIIV7FSFCJNNFWMJZTTV7NFJV2/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YKD5WEFA4WT6AVTMRAYBNXZNLWZHM7FH/', 'https://packagist.org/packages/pear/archive_tar', 'https://github.com/pear/Archive_Tar/releases/tag/1.4.13', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VJQQYDAOWHD6RDITDRPHFW7WY6BS3V5N/', 'https://security.gentoo.org/glsa/202101-23', 'https://github.com/pear/Archive_Tar', 'https://www.drupal.org/sa-core-2021-001', 'https://github.com/pear/Archive_Tar/issues/35', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00018.html'}
| null |
Packagist
|
GHSA-j545-frh3-r9gq
|
SQL Injection in dolibarr
|
dolibarr is vulnerable to Improper Neutralization of Special Elements used in an SQL Command
|
{'CVE-2022-0224'}
|
2022-01-19T17:41:41Z
|
2022-01-21T23:56:39Z
|
HIGH
| null |
{'CWE-89'}
|
{'https://huntr.dev/bounties/f1d1ce3e-ca92-4c7b-b1b8-934e28eaa486', 'https://github.com/dolibarr/dolibarr', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0224', 'https://github.com/dolibarr/dolibarr/commit/b9b45fb50618aa8053961f50bc8604b188d0ea79'}
| null |
Packagist
|
GHSA-6gr8-c3m5-mvrg
|
Exposure of Sensitive Information to an Unauthorized Actor
|
Shopware is an open source eCommerce platform. In versions prior to 6.4.1.1 private files publicly accessible with Cloud Storage providers when the hashed URL is known. Users are recommend to first change their configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`. When the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html. Otherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities.
|
{'CVE-2021-32717'}
|
2021-06-25T15:26:54Z
|
2021-09-08T18:00:47Z
|
HIGH
| null |
{'CWE-200'}
|
{'https://github.com/shopware/platform/security/advisories/GHSA-vrf2-xghr-j52v', 'https://github.com/shopware/platform/commit/ba52f683372b8417a00e9014f481ed3d539f34b3', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-06-2021', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32717'}
| null |
Packagist
|
GHSA-79jw-2f46-wv22
|
Authenticated remote code execution in October CMS
|
### Impact
An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass `cms.safe_mode` / `cms.enableSafeMode` in order to execute arbitrary code.
- This issue only affects admin panels that rely on safe mode and restricted permissions.
- To exploit this vulnerability, an attacker must first have access to the backend area.
### Patches
The issue has been patched in Build 474 (v1.0.474) and v1.1.10.
### Workarounds
Apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installation manually if unable to upgrade to Build 474 or v1.1.10.
### References
Credits to:
- David Miller
### For more information
If you have any questions or comments about this advisory:
- Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
|
{'CVE-2022-21705'}
|
2022-02-25T15:37:37Z
|
2022-02-23T21:08:44Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe', 'https://github.com/octobercms/october/security/advisories/GHSA-79jw-2f46-wv22', 'https://github.com/octobercms/october/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21705'}
| null |
Packagist
|
GHSA-cg8j-8w52-735v
|
Missing warning can lead to unauthenticated admin access in SilverStripe
|
In SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to unauthenticated admin access.
|
{'CVE-2019-12204'}
|
2021-12-03T14:39:16Z
|
2019-11-12T23:01:25Z
|
CRITICAL
| null | null |
{'https://packagist.org/packages/silverstripe/cms', 'https://packagist.org/packages/silverstripe/framework', 'https://www.silverstripe.org/download/security-releases/', 'https://forum.silverstripe.org/c/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12204', 'https://www.silverstripe.org/download/security-releases/CVE-2019-12204'}
| null |
Packagist
|
GHSA-2r3v-q9x3-7g46
|
Link injection in SimpleSAMLphp
|
### Background
Several scripts part of SimpleSAMLphp display a web page with links obtained from the request parameters. This allows us to enhance usability, as the users are presented with links they can follow after completing a certain action, like logging out.
### Description
The following scripts were not checking the URLs obtained via the HTTP request before displaying them as the target of links that the user may click on:
- `www/logout.php`
- `modules/core/www/no_cookie.php`
The issue allowed attackers to display links targeting a malicious website inside a trusted site running SimpleSAMLphp, due to the lack of security checks involving the `link_href` and `retryURL` HTTP parameters, respectively. The issue was resolved by including a verification of the URLs received in the request against a white list of websites specified in the `trusted.url.domains` configuration option.
### Affected versions
All SimpleSAMLphp versions prior to 1.14.4.
### Impact
A remote attacker could craft a link pointing to a trusted website running SimpleSAMLphp, including a parameter pointing to a malicious website, and try to fool the victim into visiting that website by clicking on a link in the page presented by SimpleSAMLphp.
### Resolution
Upgrade to the latest version.
### Credit
This security issue was discovered and reported by John Page (hyp3rlinx).
| null |
2021-08-19T16:31:00Z
|
2020-01-24T21:27:16Z
|
LOW
| null |
{'CWE-74'}
|
{'https://snyk.io/vuln/SNYK-PHP-SIMPLESAMLPHPSIMPLESAMLPHP-70160', 'https://github.com/simplesamlphp/simplesamlphp/security/advisories/GHSA-2r3v-q9x3-7g46'}
| null |
Packagist
|
GHSA-6jhm-4vmx-mr76
|
SQL injection in Moodle
|
A flaw was found in Moodle in versions 3.11 to 3.11.4. An SQL injection risk was identified in the h5p activity web service responsible for fetching user attempt data.
|
{'CVE-2022-0332'}
|
2022-02-02T16:11:16Z
|
2022-01-28T22:08:14Z
|
CRITICAL
| null |
{'CWE-89'}
|
{'https://bugzilla.redhat.com/show_bug.cgi?id=2043661', 'https://github.com/moodle/moodle/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0332', 'https://github.com/moodle/moodle/commit/c7a62a8c82219b50589257f79021da1df1a76808', 'https://moodle.org/mod/forum/discuss.php?d=431099'}
| null |
Packagist
|
GHSA-4x2f-54wr-4hjg
|
Potential Zip Slip Vulnerability in baserCMS
|
There is a OS Command Injection Vulnerability on the management system of baserCMS.
This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.
If you are eligible, please update to the new version as soon as possible.
Target
baserCMS 4.5.3 and earlier versions
Vulnerability
OS Command Injection Vulnerability.
Countermeasures
Update to the latest version of baserCMS
Credits
Daniele Scanu @SoterItSecurity
|
{'CVE-2021-41279'}
|
2021-11-29T19:15:58Z
|
2021-12-01T18:29:32Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/baserproject/basercms/security/advisories/GHSA-4x2f-54wr-4hjg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41279', 'https://github.com/baserproject/basercms', 'https://github.com/baserproject/basercms/commit/d8ab0a81a7bce35cc95ff7dff851a7e87a084336'}
| null |
Packagist
|
GHSA-p62j-hrxm-xcxf
|
Book page text, count, and author/title length is not limited in PocketMine-MP
|
### Impact
Players can fill book pages with as many characters as they like; the server does not check this.
In addition, the maximum of 50 pages is also not enforced, meaning that players can create "book bombs".
This causes a variety of problems:
- Oversized NBT on the wire costing excess bandwidth for server and client
- Server crashes when saving region-based worlds due to exceeding maximum chunk size of 1 MB (PM3-specific)
- Server crashes if any book page exceeds 32 KiB (due to TAG_String size limit) (PM4-specific)
This does, however, require that an attacker obtain a writable book in the first place in order to exploit the problem.
### Patches
The bug has been fixed in 3.26.5 and 4.0.5.
### Workarounds
Ban writable books, or use a plugin to cancel `PlayerEditBookEvent` to cancel the event if `strlen(text) > 1024 || mb_strlen(text) > 256`.
### For more information
If you have any questions or comments about this advisory:
* Email us at [team@pmmp.io](mailto:team@pmmp.io)
| null |
2022-01-06T19:44:35Z
|
2022-01-06T23:53:35Z
|
MODERATE
| null | null |
{'https://github.com/pmmp/PocketMine-MP', 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-p62j-hrxm-xcxf'}
| null |
Packagist
|
GHSA-x28w-hvwc-mp75
|
Static Code Injection in Microweber
|
Microweber is a new generation CMS with drag and drop. Prior to version 1.3, Microweber is vulnerable to static code injection.
|
{'CVE-2022-0895'}
|
2022-03-25T17:18:05Z
|
2022-03-11T00:02:35Z
|
HIGH
| null |
{'CWE-94', 'CWE-96'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0895', 'https://github.com/microweber/microweber/commit/b2baab6e582b2efe63788d367a2bb61a2fa26470', 'https://github.com/microweber/microweber', 'https://huntr.dev/bounties/3c070828-fd00-476c-be33-9c877172363d'}
| null |
Packagist
|
GHSA-2frx-j9hj-6c65
|
User enumeration in authentication mechanisms
|
Description
-----------
The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not.
Resolution
----------
We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist.
The patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x.
Credits
-------
I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.
| null |
2021-10-08T21:21:39Z
|
2021-05-17T20:52:21Z
|
LOW
| null |
{'CWE-200'}
|
{'https://github.com/lexik/LexikJWTAuthenticationBundle/', 'https://github.com/lexik/LexikJWTAuthenticationBundle/security/advisories/GHSA-2frx-j9hj-6c65', 'https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7'}
| null |
Packagist
|
GHSA-vc5r-xfc4-4x22
|
Cross-site Scripting in Pimcore Datahub
|
Pimcore Datahub prior to 1.2.4 is vulnerable to stored cross-site scripting. An admin user accessing Datahub triggers the attack, which may result in the user's cookie being stolen.
|
{'CVE-2022-0955'}
|
2022-03-30T21:03:02Z
|
2022-03-25T00:00:33Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/pimcore/data-hub', 'https://huntr.dev/bounties/708971a6-1e6c-4c51-a411-255caeba51df', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0955', 'https://github.com/pimcore/data-hub/commit/15d5b57af2466eebd3bbc531ead5dafa35d0a36e'}
| null |
Packagist
|
GHSA-vpmw-77vm-4mjg
|
Cross-site Scripting in Cipi
|
Cipi 3.1.15 allows Add Server stored cross-site scripting via the /api/servers name field.
|
{'CVE-2022-26332'}
|
2022-03-09T20:07:17Z
|
2022-03-02T00:00:21Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-26332', 'https://github.com/andreapollastri/cipi', 'https://github.com/andreapollastri/cipi/releases', 'https://www.exploit-db.com/exploits/50788'}
| null |
Packagist
|
GHSA-xpxm-pf7g-2534
|
Cross-site scripting in media2click
|
The media2click (aka 2 Clicks for External Media) extension 1.x before 1.3.3 for TYPO3 allows XSS by a backend user account.
|
{'CVE-2021-31778'}
|
2021-05-03T16:41:32Z
|
2021-06-08T20:11:52Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-31778', 'https://packagist.org/packages/amazing/media2click', 'https://typo3.org/security/advisory/typo3-ext-sa-2021-004', 'https://github.com/ghermens/media2click/commit/3c4e413fbc7d35c47212e754c24d5070637a11a3'}
| null |
Packagist
|
GHSA-mrq4-7ch7-2465
|
Server Side Twig Template Injection
|
PrestaShop is an Open Source e-commerce platform. Starting with version 1.7.0.0 and ending with version 1.7.8.3, an attacker is able to inject twig code inside the back office when using the legacy layout. The problem is fixed in version 1.7.8.3. There are no known workarounds.
|
{'CVE-2022-21686'}
|
2022-02-07T21:21:25Z
|
2022-01-27T18:32:47Z
|
CRITICAL
| null |
{'CWE-94'}
|
{'https://github.com/PrestaShop/PrestaShop/releases/tag/1.7.8.3', 'https://github.com/PrestaShop/PrestaShop/', 'https://github.com/PrestaShop/PrestaShop/commit/d02b469ec365822e6a9f017e57f588966248bf21', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21686', 'https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-mrq4-7ch7-2465'}
| null |
Packagist
|
GHSA-rw98-5846-pqhx
|
Open redirect in microweber
|
Open Redirect in Packagist microweber/microweber prior to 1.2.11.
|
{'CVE-2022-0597'}
|
2022-02-24T13:56:27Z
|
2022-02-16T00:01:45Z
|
MODERATE
| null |
{'CWE-601'}
|
{'https://github.com/microweber/microweber', 'https://huntr.dev/bounties/68c22eab-cc69-4e9f-bcb6-2df3db626813', 'https://github.com/microweber/microweber/commit/acfc6a581d1ea86096d1b0ecd8a0eec927c0e9b2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0597'}
| null |
Packagist
|
GHSA-qm58-cvvm-c5qr
|
Unsafe upload filtering leading to remote code execution
|
### Impact
Before elFinder 2.1.58, the upload filter did not disallow the upload of `.phar` files. As several Linux distributions are now shipping Apache configured in a way it will process these files as PHP scripts, attackers could gain arbitrary code execution on the server hosting the PHP connector (even in minimal configuration).
### Patches
The issue has been addressed with https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1, associating `.phar` files to the right MIME type. Unless explicitly allowed in the configuration, such files cannot be uploaded anymore. This patch is part of the last release of elFinder, 2.1.58.
### Workarounds
If you can't update to 2.1.58, make sure your connector is not exposed without authentication.
### Important tips
Server-side scripts can often be created as text files. Currently, elFinder has an appropriate MIME type set for file extensions that are generally runnable on a web server.
However, the server has various settings. In some cases, the executable file may be judged as "text/plain". Therefore, elFinder installers should understand the extensions that can be executed on the web server where elFinder is installed, and check if there are any missing items in the elFinder settings.
The elFinder PHP connector has an option "additionalMimeMap" that specifies the MIME type for each extension. See [#3295(comment)](https://github.com/Studio-42/elFinder/issues/3295#issuecomment-853042139) for more information.
### References
- https://snyk.io/vuln/composer:studio-42%2Felfinder
- https://github.com/Studio-42/elFinder/issues/3295
- Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.
### For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to support [at] snyk.io or vulnerability.research [at] sonarsource.com;
- The maintainers, by opening an issue on this repository.
|
{'CVE-2021-23394'}
|
2021-07-13T15:49:28Z
|
2021-06-15T15:51:02Z
|
HIGH
| null |
{'CWE-434'}
|
{'https://github.com/Studio-42/elFinder', 'https://snyk.io/vuln/SNYK-PHP-STUDIO42ELFINDER-1290554', 'https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1', 'https://github.com/Studio-42/elFinder/security/advisories/GHSA-qm58-cvvm-c5qr', 'https://github.com/Studio-42/elFinder/issues/3295', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23394'}
| null |
Packagist
|
GHSA-qvrv-2x7x-78x2
|
Reflected XSS in SilverStripe
|
SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user&#39;s credentials or other sensitive user input.
|
{'CVE-2019-19325'}
|
2021-08-19T17:22:37Z
|
2020-02-24T17:33:31Z
|
MODERATE
| null |
{'CWE-78'}
|
{'https://www.silverstripe.org/download/security-releases/cve-2019-19325', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19325', 'https://github.com/silverstripe/silverstripe-framework/commit/49fda52b12ba59f0a04bcabf78425586a8779e89'}
| null |
Packagist
|
GHSA-29gp-2c3m-3j6m
|
Sandbox Escape by math function in smarty
|
### Impact
Template authors could run arbitrary PHP code by crafting a malicious math string.
If a math string is passed through as user provided data to the math function, external users could run arbitrary PHP code by crafting a malicious math string.
### Patches
Please upgrade to 4.0.2 or 3.1.42 or higher.
### References
See [documentation on Math function](https://www.smarty.net/docs/en/language.function.math.tpl).
### For more information
If you have any questions or comments about this advisory please open an issue in [the Smarty repo](https://github.com/smarty-php/smarty)
|
{'CVE-2021-29454'}
|
2022-01-20T15:34:11Z
|
2022-01-12T22:43:00Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://github.com/smarty-php/smarty/security/advisories/GHSA-29gp-2c3m-3j6m', 'https://github.com/smarty-php/smarty/releases/tag/v4.0.2', 'https://github.com/smarty-php/smarty/releases/tag/v3.1.42', 'https://github.com/smarty-php/smarty', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29454', 'https://github.com/smarty-php/smarty/commit/215d81a9fa3cd63d82fb3ab56ecaf97cf1e7db71', 'https://packagist.org/packages/smarty/smarty', 'https://www.smarty.net/docs/en/language.function.math.tpl'}
| null |
Packagist
|
GHSA-fqx8-v33p-4qcc
|
Cross-site Scripting in enshrined/svg-sanitize
|
### Impact
SVG sanitizer library before version `0.15.0` did not remove HTML elements wrapped in a CDATA section. As a result, SVG content embedded in HTML (fetched as `text/html`) was susceptible to cross-site scripting. Plain SVG files (fetched as `image/svg+xml`) were not affected.
### Patches
This issue is fixed in `0.15.0` and higher.
### Workarounds
There is currently no workaround available without upgrading.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Github](https://github.com/darylldoyle/svg-sanitizer/issues)
* Email us at [daryll@enshrined.co.uk](mailto:daryll@enshrined.co.uk)
|
{'CVE-2022-23638'}
|
2022-03-09T23:27:04Z
|
2022-02-14T22:54:18Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/darylldoyle/svg-sanitizer/issues/71', 'https://github.com/darylldoyle/svg-sanitizer/security/advisories/GHSA-fqx8-v33p-4qcc', 'https://github.com/darylldoyle/svg-sanitizer', 'https://github.com/darylldoyle/svg-sanitizer/commit/17e12ba9c2881caa6b167d0fbea555c11207fbb0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23638'}
| null |
Packagist
|
GHSA-rwgm-f83r-v3qj
|
Improper Certificate Validation in WP-CLI framework
|
### Impact
An improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself.
### Patches
The vulnerability stems from the fact that the default behavior of `WP_CLI\Utils\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request.
The default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\Utils\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\Utils\http_request()`, including those in separate WP-CLI bundled or third-party packages.
https://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change.
Subsequent PRs on the command repositories have added an `--insecure` flag to the appropriate commands on the following repositories to counter the breaking change:
* https://github.com/wp-cli/config-command/pull/128
* https://github.com/wp-cli/core-command/pull/186
* https://github.com/wp-cli/extension-command/pull/287
* https://github.com/wp-cli/checksum-command/pull/86
* https://github.com/wp-cli/package-command/pull/138
### Workarounds
There is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0.
The workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior.
### References
* [CWE: Improper Certificate Validation](https://cwe.mitre.org/data/definitions/295.html)
### For more information
If you have any questions or comments about this advisory:
* Join the `#cli` channel in the [WordPress.org Slack](https://make.wordpress.org/chat/) to ask questions or provide feedback.
|
{'CVE-2021-29504'}
|
2021-06-18T20:29:34Z
|
2021-05-19T23:03:11Z
|
CRITICAL
| null |
{'CWE-295'}
|
{'https://github.com/wp-cli/extension-command/pull/287', 'https://github.com/wp-cli/core-command/pull/186', 'https://github.com/wp-cli/wp-cli/pull/5523', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29504', 'https://github.com/wp-cli/checksum-command/pull/86', 'https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj', 'https://github.com/wp-cli/package-command/pull/138', 'https://github.com/wp-cli/config-command/pull/128'}
| null |
Packagist
|
GHSA-5qjq-69w6-fg57
|
XSS vulnerability with translator
|
Flarum's translation system allowed for string inputs to be converted into HTML DOM nodes when rendered. This change was made after v0.1.0-beta.16 (our last beta before v1.0.0) and was not noticed or documented.
This allowed for any user to type malicious HTML markup within certain user input fields and have this execute on client browsers. The example which led to the discovery of this vulnerability was in the forum search box. Entering faux-malicious HTML markup, such as <script>alert('test')</script> resulted in an alert box appearing on the forum. This attack could also be modified to perform AJAX requests on behalf of a user, possibly deleting discussions, modifying their settings or profile, or even modifying settings on the Admin panel if the attack was targetted towards a privileged user.
### Impact
All Flarum communities that run flarum v1.0.0 or v1.0.1 are impacted.
### Patches
The vulnerability has been fixed and published as flarum/core v1.0.2. All communities running Flarum v1.0 have to upgrade as soon as possible to v1.0.2 using:
```
composer update --prefer-dist --no-dev -a -W
```
You can then confirm you run the latest version using:
```
composer show flarum/core
```
### Workarounds
__None.__
### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.
For support questions create a discussion at https://discuss.flarum.org/t/support.
A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly.
|
{'CVE-2021-32671'}
|
2021-06-07T21:05:48Z
|
2021-06-07T21:48:17Z
|
CRITICAL
| null |
{'CWE-79'}
|
{'https://github.com/flarum/core/security/advisories/GHSA-5qjq-69w6-fg57', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32671', 'https://packagist.org/packages/flarum/core', 'https://github.com/flarum/core/commit/440bed81b8019dff00642c8f493b4909d505a28a'}
| null |
Packagist
|
GHSA-gc45-j3m5-8qfq
|
Server-Side Request Forgery in Feehi CMS
|
Feehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.
|
{'CVE-2021-30108'}
|
2021-05-28T21:56:18Z
|
2021-06-08T20:12:32Z
|
CRITICAL
| null |
{'CWE-918'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-30108', 'https://github.com/liufee/cms/issues/57'}
| null |
Packagist
|
GHSA-46rx-6jg9-4fh8
|
Cross-site Scripting in LibreNMS
|
LibreNMS through 21.10.2 allows XSS via a widget title.
|
{'CVE-2021-43324'}
|
2021-11-08T17:58:59Z
|
2021-11-08T17:59:15Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-43324', 'https://github.com/librenms/librenms', 'https://github.com/librenms/librenms/commit/99d2462b80435b91a35236639b909eebee432126'}
| null |
Packagist
|
GHSA-2r6j-862c-m2v2
|
Unrestricted File Upload in Form Framework
|
### Problem
Due to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.
TYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.
In any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.
No authentication is required to exploit this vulnerability.
### Solution
Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
Type converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uploaded files within the scope of the Form Framework. Guessable storage location has changed from _/fileadmin/user_upload/form\_\<random-hash\>/_ to _/fileadmin/form_uploads/<random-40-bit>_. Allowed mime-types must match expected file extensions (e.g. _application/pdf_ must be _.pdf_, and cannot be _.html_).
Extbase extensions, who rely on the global availability of the _UploadedFileReferenceConverter_ must now implement a custom _TypeConverter_ to handle file uploads or explicitly implement the ext:form _UploadedFileReferenceConverter_ with appropriate setting for accepted mime-types.
### Credits
Thanks to Sebastian Michaelsen, Marc Lindemann, Oliver Eglseder, Markus Volkmer, Jakob Kunzmann, Johannes Regner, Richie Lee who reported this issue, and to TYPO3 core & security team members Oliver Hader & Benni Mack, as well as TYPO3 contributor Ralf Zimmermann who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-002](https://typo3.org/security/advisory/typo3-core-sa-2021-002)
|
{'CVE-2021-21355'}
|
2021-03-29T18:01:54Z
|
2021-03-23T01:53:52Z
|
HIGH
| null |
{'CWE-434', 'CWE-552'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-21355', 'https://packagist.org/packages/typo3/cms-form', 'https://typo3.org/security/advisory/typo3-core-sa-2021-002', 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2r6j-862c-m2v2'}
| null |
Packagist
|
GHSA-vhgr-gfx3-fg37
|
Unrestricted Upload of File with Dangerous Type in WPanel 4
|
Multiple Remote Code Execution (RCE) vulnerabilities exist in WPanel 4 4.3.1 and below via a malicious PHP file upload to (1) Dashboard's Avatar image, (2) Posts Folder image, (3) Pages Folder image and (4) Gallery Folder image.
|
{'CVE-2021-34257'}
|
2022-04-12T20:35:52Z
|
2022-04-01T00:00:41Z
|
HIGH
| null |
{'CWE-434'}
|
{'https://latestpcsolution.wordpress.com/2021/06/05/wpanel4-cms-authenticated-rce/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-34257', 'https://github.com/Sentinal920/WPanel4-Authenticated-RCE', 'https://github.com/wpanel/wpanel4-cms'}
| null |
Packagist
|
GHSA-4rmr-c2jx-vx27
|
Remote code injection in mustache/mustache
|
In Mustache.php v2.0.0 through v2.14.0, Sections tag can lead to arbitrary php code execution even if strict_callables is true when section value is controllable.
|
{'CVE-2022-0323'}
|
2022-01-28T18:22:21Z
|
2022-01-27T14:51:00Z
|
HIGH
| null |
{'CWE-1336'}
|
{'https://github.com/bobthecow/mustache.php', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0323', 'https://github.com/bobthecow/mustache.php/commit/579ffa5c96e1d292c060b3dd62811ff01ad8c24e', 'https://huntr.dev/bounties/a5f5a988-aa52-4443-839d-299a63f44fb7'}
| null |
Packagist
|
GHSA-5q58-x5h2-v5rx
|
Authenticated Privilege Escalation
|
### Impact
Authenticated Privilege Escalation
### Patches
We recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020
| null |
2020-12-21T17:43:25Z
|
2020-12-21T18:01:08Z
|
LOW
| null |
{'CWE-863'}
|
{'https://github.com/shopware/platform/security/advisories/GHSA-5q58-x5h2-v5rx'}
| null |
Packagist
|
GHSA-657m-v5vm-f6rw
|
Cross-Site-Request-Forgery in Backend
|
> ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2)
### Problem
It has been discovered that the new TYPO3 v11 feature that allows users to create and share [deep links in the backend user interface](https://typo3.org/article/typo3-version-112-escape-the-orbit#c12178) is vulnerable to cross-site-request-forgery.
The impact is the same as described in [TYPO3-CORE-SA-2020-006 (CVE-2020-11069)](https://typo3.org/security/advisory/typo3-core-sa-2020-006). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.
To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.
The following [Same-Site cookie settings](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-90351-ConfigureTYPO3-shippedCookiesWithSameSiteFlag.html) in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful:
* _SameSite=_***strict***: malicious evil.**example.org** invoking TYPO3 application at good.**example.org**
* _SameSite=_***lax*** or ***none***: malicious **evil.com** invoking TYPO3 application at **example.org**
### Solution
Update your instance to TYPO3 version 11.5.0 which addresses the problem described.
### Credits
Thanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-014](https://typo3.org/security/advisory/typo3-core-sa-2021-014)
* [CVE-2020-11069](https://nvd.nist.gov/vuln/detail/CVE-2020-11069) reintroduced in TYPO3 v11.2.0
|
{'CVE-2021-41113'}
|
2021-11-01T21:06:16Z
|
2021-10-05T20:23:47Z
|
MODERATE
| null |
{'CWE-352', 'CWE-309'}
|
{'https://typo3.org/security/advisory/typo3-core-sa-2020-006', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41113', 'https://github.com/TYPO3/typo3/security/advisories/GHSA-657m-v5vm-f6rw', 'https://github.com/TYPO3/typo3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11069', 'https://github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f'}
| null |
Packagist
|
GHSA-w4rc-rx25-8m86
|
Improper Input Validation in Symfony
|
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
|
{'CVE-2019-11325'}
|
2021-08-19T17:13:33Z
|
2020-02-12T18:44:16Z
|
CRITICAL
| null |
{'CWE-116'}
|
{'https://symfony.com/cve-2019-11325', 'https://symfony.com/blog/cve-2019-11325-fix-escaping-of-strings-in-varexporter', 'https://github.com/symfony/var-exporter/compare/d8bf442...57e00f3', 'https://github.com/symfony/symfony/releases/tag/v4.3.8', 'https://symfony.com/blog/symfony-4-3-8-released', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2019-11325.yaml', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/var-exporter/CVE-2019-11325.yaml', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11325'}
| null |
Packagist
|
GHSA-4p3x-8qw9-24w9
|
Authenticated Stored XSS in shopware/shopware
|
### Impact
Authenticated Stored XSS in Administration
### Patches
Use the Security Plugin:
https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html
### Workarounds
If you cannot use the security plugin, add the following config to your `.htaccess` file
```
<IfModule mod_headers.c>
<FilesMatch "\.(?i:svg)$">
Header set Content-Security-Policy "script-src 'none'"
</FilesMatch>
</IfModule>
```
If you are using nginx as server config, you can add the following to your configuration:
```
server {
# ...
location ~* ^.+\.svg$ {
add_header Content-Security-Policy "script-src 'none'";
}
}
```
### References
https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021
|
{'CVE-2021-41188'}
|
2021-10-26T17:56:23Z
|
2021-10-27T18:53:18Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/shopware/shopware/security/advisories/GHSA-4p3x-8qw9-24w9', 'https://github.com/shopware/shopware/commit/37213e91d525c95df262712cba80d1497e395a58', 'https://github.com/shopware/shopware/releases/tag/v5.7.6', 'https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021', 'https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html', 'https://github.com/shopware/shopware', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41188'}
| null |
Packagist
|
GHSA-7wv8-g97r-432h
|
Exposure of Sensitive Information to an Unauthorized Actor in microweber
|
Exposure of Sensitive Information to an Unauthorized Actor in Packagist microweber/microweber prior to 1.2.11.
|
{'CVE-2022-0281'}
|
2022-01-27T18:32:04Z
|
2022-01-21T18:06:47Z
|
HIGH
| null |
{'CWE-200'}
|
{'https://github.com/microweber/microweber', 'https://github.com/microweber/microweber/commit/e680e134a4215c979bfd2eaf58336be34c8fc6e6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0281', 'https://huntr.dev/bounties/315f5ac6-1b5e-4444-ad8f-802371da3505'}
| null |
Packagist
|
GHSA-wrxc-mr2w-cjpv
|
Open Redirect in Grav
|
Common/Grav.php in Grav before 1.6.23 has an Open Redirect.
|
{'CVE-2020-11529'}
|
2021-05-19T22:30:40Z
|
2022-01-07T00:20:50Z
|
MODERATE
| null |
{'CWE-601'}
|
{'https://github.com/getgrav/grav/issues/3134', 'https://github.com/getgrav/grav/commit/2eae104c7a4bf32bc26cb8073d5c40464bfda3f7', 'https://getgrav.org/#changelog', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11529'}
| null |
Packagist
|
GHSA-p885-prv3-m4xv
|
Cross-site Scripting in snipe-it
|
Stored Cross Site Scripting vulnerability in Item name parameter in GitHub repository snipe/snipe-it prior to v5.4.3. The vulnerability is capable of stolen the user Cookie.
|
{'CVE-2022-1380'}
|
2022-04-27T20:26:41Z
|
2022-04-17T00:00:32Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/snipe/snipe-it/commit/f211c11034baf4281aa62e7b5e0347248d995ee9', 'https://huntr.dev/bounties/3d45cfca-3a72-4578-b735-98837b998a12', 'https://github.com/snipe/snipe-it', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1380'}
| null |
Packagist
|
GHSA-8qv8-fq5w-p966
|
phpservermon is vulnerable to CRLF Injection
|
phpservermon is vulnerable to Improper Neutralization of CRLF Sequences.
|
{'CVE-2021-4097'}
|
2021-12-16T14:09:58Z
|
2021-12-16T14:26:00Z
|
MODERATE
| null |
{'CWE-93'}
|
{'https://github.com/phpservermon/phpservermon', 'https://github.com/phpservermon/phpservermon/commit/162bba0046fcda1580f4fbc7b9ababe3c7c13ce4', 'https://huntr.dev/bounties/d617ced7-be06-4e34-9db0-63d45c003a43', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4097'}
| null |
Packagist
|
GHSA-7q44-r25x-wm4q
|
Remote Code Execution vulnerability in PHPMailer 6.4.1 running on Windows
|
PHPMailer 6.4.1 contains a possible remote code execution vulnerability through the `$lang_path` parameter of the `setLanguage()` method. If the `$lang_path` parameter is passed unfiltered from user input, it can be set to [a UNC path](https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-paths), and if an attacker is also able to create a remote mount on the server that the UNC path points to, a script file under their control may be executed.
### Impact
Arbitrary code may be run by a remote attacker under the web server or PHP process running on Window hosts.
### Patches
Mitigated in PHPMailer 6.5.0 by no longer treating translation files as PHP code, but by parsing their text content directly.
This approach avoids the possibility of executing unknown code while retaining backward compatibility. This isn't ideal, so the current translation format is deprecated and will be replaced in the next major release.
### Workarounds
Any of:
* Ensure that calling code does not pass unfiltered user-supplied data to the `$lang_path` parameter of the `setLanguage()` method.
* Block or filter the use of unknown UNC paths in this parameter (or altogether).
* Ensure that unauthorised users do not have the ability to read from unknown remote servers via UNC paths.
* Run on an OS that does not support UNC paths
### References
[CVE-2021-34551](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-34551).
Reported by [listensec.com](https://listensec.com) via Tidelift.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [PHPMailer](https://github.com/PHPMailer/PHPMailer)
* [Email the maintainers](mailto:phpmailer@synchromedia.co.uk)
|
{'CVE-2021-34551'}
|
2021-06-30T18:13:17Z
|
2021-06-22T15:17:51Z
|
HIGH
| null |
{'CWE-94', 'CWE-434'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FJYSOFCUBS67J3TKR74SD3C454N7VTYM/', 'https://github.com/PHPMailer/PHPMailer/blob/master/SECURITY.md', 'https://github.com/PHPMailer/PHPMailer/commit/acd264bf17ff4ac5c915f0d4226dce8a9ea70bc3', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YRMWGA4VTMXFB22KICMB7YMFZNFV3EJ/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-34551', 'https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-7q44-r25x-wm4q'}
| null |
Packagist
|
GHSA-fcr8-6q7r-m4wg
|
Bypass of fix for CVE-2020-26231, Twig sandbox escape
|
### Impact
A bypass of CVE-2020-26231 (fixed in 1.0.470/471 and 1.1.1) was discovered that has the same impact as CVE-2020-26231 & CVE-2020-15247:
An authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.
This is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.
### Patches
Issue has been patched in Build 472 (v1.0.472) and v1.1.2.
### Workarounds
Apply https://github.com/octobercms/october/commit/f63519ff1e8d375df30deba63156a2fc97aa9ee7 to your installation manually if unable to upgrade to Build 472 or v1.1.2.
### References
Reported by [ka1n4t](https://github.com/ka1n4t)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1108" alt="Screen Shot 2020-10-10 at 1 21 13 PM" src="https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png">
|
{'CVE-2021-21264'}
|
2021-05-13T15:05:58Z
|
2021-05-04T17:42:33Z
|
MODERATE
| null |
{'CWE-862'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-21264', 'https://github.com/octobercms/october/security/advisories/GHSA-fcr8-6q7r-m4wg'}
| null |
Packagist
|
GHSA-xvvv-wj7j-r9jm
|
Cross-site Scripting in Netgen Tags Bundle
|
Netgen Tags Bundle 3.4.x before 3.4.11 and 4.0.x before 4.0.15 allows XSS in the Tags Admin interface.
|
{'CVE-2021-45895'}
|
2022-01-05T21:32:08Z
|
2022-01-06T22:04:19Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/netgen/TagsBundle', 'https://github.com/netgen/TagsBundle/releases/tag/3.4.11', 'https://github.com/netgen/TagsBundle/releases/tag/4.0.15', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45895'}
| null |
Packagist
|
GHSA-w4f3-7f7c-x652
|
SQL Injection in tribalsystems/zenario
|
SQL Injection in Tribalsystems Zenario CMS 8.8.52729 and prior allows remote attackers to access the database or delete the plugin. This is accomplished via the `ID` input field of ajax.php in the `Pugin library - delete` module.
|
{'CVE-2021-26830'}
|
2022-03-18T17:49:01Z
|
2022-03-18T17:49:01Z
|
CRITICAL
| null |
{'CWE-89'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-26830', 'https://github.com/TribalSystems/Zenario/commit/2c82a4d126c8446106347ef603b157f2d4175fd1', 'https://github.com/TribalSystems/Zenario/releases/tag/8.8.53370'}
| null |
Packagist
|
GHSA-qhrx-hcm6-pmrw
|
Unsafe deserialization in SmtpTransport in CakePHP
|
An issue was discovered in SmtpTransport in CakePHP 3.7.6. An unserialized object with modified internal properties can trigger arbitrary file overwriting upon destruction.
|
{'CVE-2019-11458'}
|
2021-08-19T15:25:20Z
|
2019-12-02T18:12:26Z
|
HIGH
| null |
{'CWE-502'}
|
{'https://github.com/cakephp/cakephp/commits/master', 'https://github.com/cakephp/cakephp/commit/1a74e798309192a9895c9cedabd714ceee345f4e', 'https://bakery.cakephp.org/2019/04/23/cakephp_377_3615_3518_released.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11458', 'https://github.com/cakephp/cakephp/releases', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/cakephp/cakephp/CVE-2019-11458.yaml', 'https://github.com/cakephp/cakephp/compare/3.7.6...3.7.7'}
| null |
Packagist
|
GHSA-r7rh-g777-g5gx
|
SilverStripe GraphQL Server permission checker not inherited by query subclass.
|
Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.
|
{'CVE-2021-28661'}
|
2021-10-18T14:34:41Z
|
2021-10-12T18:49:23Z
|
MODERATE
| null |
{'CWE-863'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-28661', 'https://github.com/silverstripe/silverstripe-graphql/releases', 'https://github.com/silverstripe/silverstripe-graphql/pull/407/commits/16961459f681f7b32145296189dfdbcc7715e6ed', 'https://github.com/silverstripe/silverstripe-graphql/releases/tag/3.5.2', 'https://www.silverstripe.org/download/security-releases/CVE-2021-28661', 'https://github.com/silverstripe/silverstripe-graphql'}
| null |
Packagist
|
GHSA-jrgf-vfw2-hj26
|
RCE via PHP Object injection via SOAP Requests
|
### Impact
This vulnerability allows an admin user to generate soap credentials that can be used to trigger RCE via PHP Object Injection through product attributes and a product.
### Patches
The latest OpenMage Versions up from 19.4.7 and 20.0.3 have this Issue solved
### Credits
Credit to Luke Rodgers for reporting
|
{'CVE-2020-15244'}
|
2021-11-19T13:46:38Z
|
2020-10-30T17:06:06Z
|
HIGH
| null |
{'CWE-502', 'CWE-74'}
|
{'https://github.com/OpenMage/magento-lts', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-jrgf-vfw2-hj26', 'https://github.com/OpenMage/magento-lts/commit/26433d15b57978fcb7701b5f99efe8332ca8630b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15244'}
| null |
Packagist
|
GHSA-54gp-qff8-946c
|
Insecure direct object reference of log files of the Import/Export feature
|
### Impact
Insecure direct object reference of log files of the Import/Export feature
### Patches
We recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
|
{'CVE-2021-37709'}
|
2021-08-26T19:36:36Z
|
2021-08-30T16:14:19Z
|
MODERATE
| null |
{'CWE-639', 'CWE-532'}
|
{'https://github.com/shopware/platform/security/advisories/GHSA-54gp-qff8-946c', 'https://github.com/shopware/platform', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37709', 'https://github.com/shopware/platform/commit/a9f52abb6eb503654c492b6b2076f8d924831fec'}
| null |
Packagist
|
GHSA-m49f-hcxp-6hm6
|
CSRF allowing an external page to trigger a user logout event
|
### Impact
A malicious user can trigger a user logout if a signed in user visits a malicious website that makes a request to the Panel's sign-out endpoint. This requires a targeted attack against a specific Panel instance, and serves only to sign a user out. **No user details are leaked, nor is any user data affected, this is simply an annoyance at worst.**
### Patches
None.
### Workarounds
None.
### For more information
If you have any questions or comments about this advisory please contact `Tactical Fish#8008` on Discord, or email `dane@pterodactyl.io`.
|
{'CVE-2021-41176'}
|
2021-10-26T17:31:33Z
|
2021-10-25T19:42:46Z
|
LOW
| null |
{'CWE-352'}
|
{'https://github.com/pterodactyl/panel/releases/tag/v1.6.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41176', 'https://github.com/pterodactyl/panel', 'https://github.com/pterodactyl/panel/commit/45999ba4ee1b2dcb12b4a2fa2cedfb6b5d66fac2', 'https://github.com/pterodactyl/panel/security/advisories/GHSA-m49f-hcxp-6hm6'}
| null |
Packagist
|
GHSA-9jxw-cfrh-jxq6
|
New line injection during configuration edition
|
### Impact
Authenticated users, regardless of their privileges (_User_ or _Admin_), can exploit a new line injection in the configuration edition feature (e.g. mail settings) and gain arbitrary code execution on the server.
### Patches
This issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of new lines characters in new configuration values.
### Workarounds
Only allow trusted source IP addresses to access to the administration dashboard.
### References
- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection
### For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
- The maintainers, by opening an issue on this repository.
|
{'CVE-2021-39172'}
|
2021-09-29T18:02:18Z
|
2021-08-30T16:11:24Z
|
HIGH
| null |
{'CWE-93'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-39172', 'https://github.com/fiveai/Cachet/security/advisories/GHSA-9jxw-cfrh-jxq6', 'https://github.com/fiveai/Cachet/releases/tag/v2.5.1', 'https://github.com/fiveai/Cachet'}
| null |
Packagist
|
GHSA-589w-hccm-265x
|
Inline attribute values were not processed.
|
### Impact
Inline attributes have not been processed escape.
If the data that came from users was not processed, then an XSS vulnerability is possible
### Patches
Fixed in 9.4.4
|
{'CVE-2020-15263'}
|
2021-01-07T22:50:45Z
|
2020-10-19T20:17:47Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/orchidsoftware/platform/commit/03f9a113b1a70bc5075ce86a918707f0e7d82169', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15263', 'https://github.com/orchidsoftware/platform/security/advisories/GHSA-589w-hccm-265x'}
| null |
Packagist
|
GHSA-4f5x-q4jc-xfcf
|
Cross-site Scripting in pimcore
|
Cross-site Scripting (XSS) - Stored in Packagist pimcore/pimcore.
|
{'CVE-2022-0262'}
|
2022-01-19T22:33:53Z
|
2022-01-21T23:31:35Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/pimcore/pimcore', 'https://huntr.dev/bounties/b38a4e14-5dcb-4e49-9990-494dc2a8fa0d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0262', 'https://github.com/pimcore/pimcore/commit/6f36e841ce55f67e2e95253dd58f80659ef166c7'}
| null |
Packagist
|
GHSA-hx77-5p88-f92r
|
livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)
|
livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)
|
{'CVE-2021-4131'}
|
2022-01-04T20:21:47Z
|
2022-01-05T20:33:55Z
|
HIGH
| null |
{'CWE-352'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-4131', 'https://github.com/livehelperchat/livehelperchat', 'https://huntr.dev/bounties/52dfac87-4fd3-4dfb-83d2-d39916764d43', 'https://github.com/livehelperchat/livehelperchat/commit/3b5d0a8a43595a7f05f2a81b76623a8d7e5ad19f'}
| null |
Packagist
|
GHSA-q88g-qx42-xfrh
|
Path traversal in bolt/core
|
Controller/Backend/FileEditController.php and Controller/Backend/FilemanagerController.php in Bolt before 4.1.13 allow Directory Traversal.
|
{'CVE-2021-27367'}
|
2021-02-24T06:53:21Z
|
2021-02-18T20:51:56Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/bolt/core/releases/tag/4.1.13', 'https://github.com/bolt/core/pull/2371', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27367', 'https://packagist.org/packages/bolt/core'}
| null |
Packagist
|
GHSA-3xpw-vhmv-cw7h
|
Command injection in czproject/git-php
|
The package czproject/git-php before 4.0.3 are vulnerable to Command Injection via git argument injection. When calling the isRemoteUrlReadable($url, array $refs = NULL) function, both the url and refs parameters are passed to the git ls-remote subcommand in a way that additional flags can be set. The additional flags can be used to perform a command injection.
|
{'CVE-2022-25866'}
|
2022-04-27T14:35:56Z
|
2022-04-26T00:00:35Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://github.com/czproject/git-php/commit/5e82d5479da5f16d37a915de4ec55e1ac78de733', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25866', 'https://github.com/czproject/git-php', 'https://github.com/czproject/git-php/releases/tag/v4.0.3', 'https://snyk.io/vuln/SNYK-PHP-CZPROJECTGITPHP-2421349'}
| null |
Packagist
|
GHSA-7528-7jg5-6g62
|
Cross-site Scripting Vulnerability in CodeIgniter4
|
### Impact
Cross-Site Scripting (XSS) vulnerability was found in `API\ResponseTrait` in Codeigniter4.
Attackers can do XSS attacks if you are using `API\ResponseTrait`.
### Patches
Upgrade to v4.1.8 or later.
### Workarounds
Do one of the following:
1. Do not use `API\ResponseTrait` nor `ResourceController`
2. Disable Auto Route and [Use Defined Routes Only](https://codeigniter4.github.io/userguide/incoming/routing.html#use-defined-routes-only)
### References
- [Cross Site Scripting (XSS) Software Attack | OWASP Foundation](https://owasp.org/www-community/attacks/xss/)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [codeigniter4/CodeIgniter4](https://github.com/codeigniter4/CodeIgniter4/issues)
* Email us at [SECURITY.md](https://github.com/codeigniter4/CodeIgniter4/blob/develop/SECURITY.md)
|
{'CVE-2022-21715'}
|
2022-01-31T21:46:37Z
|
2022-01-27T15:09:00Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-7528-7jg5-6g62', 'https://codeigniter4.github.io/userguide/incoming/routing.html#use-defined-routes-only', 'https://github.com/codeigniter4/CodeIgniter4/commit/70d881cf5322b7c32e69516aebd2273ac6a1e8dd', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21715', 'https://github.com/codeigniter4/framework'}
| null |
Packagist
|
GHSA-v6vg-pxvv-g5cq
|
Improper Privilege Management in Snipe-IT
|
Snipe-IT prior to 5.3.9 is vulnerable to improper privilege management. A user who does not have access to the supplier module may view supplier content.
|
{'CVE-2022-0579'}
|
2022-02-24T17:08:24Z
|
2022-02-15T00:02:45Z
|
MODERATE
| null |
{'CWE-269'}
|
{'https://github.com/snipe/snipe-it/commit/db0c0e790892db874573d95f8ae4268b8a011ab1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0579', 'https://huntr.dev/bounties/70a99cf4-3241-4ffc-b9ed-5c54932f3849', 'https://github.com/snipe/snipe-it'}
| null |
Packagist
|
GHSA-f7hx-fqxw-rvvj
|
Insufficient output escaping of attachment names in PHPMailer
|
### Impact
CWE-116: Incorrect output escaping.
An attachment added like this (note the double quote within the attachment name, which is entirely valid):
$mail->addAttachment('/tmp/attachment.tmp', 'filename.html";.jpg');
Will result in a message containing these headers:
Content-Type: application/octet-stream; name="filename.html";.jpg"
Content-Disposition: attachment; filename="filename.html";.jpg"
The attachment will be named `filename.html`, and the trailing `";.jpg"` will be ignored. Mail filters that reject `.html` attachments but permit `.jpg` attachments may be fooled by this.
Note that the MIME type itself is obtained automatically from the *source filename* (in this case `attachment.tmp`, which maps to a generic `application/octet-stream` type), and not the *name* given to the attachment (though these are the same if a separate name is not provided), though it can be set explicitly in other parameters to attachment methods.
### Patches
Patched in PHPMailer 6.1.6 by escaping double quotes within the name using a backslash, as per RFC822 section 3.4.1, resulting in correctly escaped headers like this:
Content-Type: application/octet-stream; name="filename.html\";.jpg"
Content-Disposition: attachment; filename="filename.html\";.jpg"
### Workarounds
Reject or filter names and filenames containing double quote (`"`) characters before passing them to attachment functions such as `addAttachment()`.
### References
[CVE-2020-13625](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-13625).
[PHPMailer 6.1.6 release](https://github.com/PHPMailer/PHPMailer/releases/tag/v6.1.6)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the PHPMailer repo](https://github.com/PHPMailer/PHPMailer/issues)
|
{'CVE-2020-13625'}
|
2021-08-25T21:37:23Z
|
2020-05-27T16:37:02Z
|
HIGH
| null |
{'CWE-116'}
|
{'https://lists.debian.org/debian-lts-announce/2020/06/msg00014.html', 'https://github.com/PHPMailer/PHPMailer', 'https://github.com/PHPMailer/PHPMailer/releases/tag/v6.1.6', 'https://usn.ubuntu.com/4505-1/', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00004.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EFM3BZABL6RUHTVMXSC7OFMP4CKWMRPJ/', 'https://github.com/PHPMailer/PHPMailer/commit/c2796cb1cb99d7717290b48c4e6f32cb6c60b7b3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13625', 'https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-f7hx-fqxw-rvvj', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SMH4TC5XTS3KZVGMSKEPPBZ2XTZCKKCX/', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00067.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00085.html'}
| null |
Packagist
|
GHSA-jjcx-999m-35hc
|
Improper Input Validation in Firefly III
|
Firefly III 4.7.17.3 is vulnerable to local file enumeration. An attacker can enumerate local files due to the lack of protocol scheme sanitization, such as for file:/// URLs. This is related to fints_url to import/job/configuration, and import/create/fints.
|
{'CVE-2019-14671'}
|
2021-07-22T21:50:38Z
|
2021-09-08T17:27:07Z
|
LOW
| null |
{'CWE-20'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-14671', 'https://github.com/firefly-iii/firefly-iii/issues/2367', 'https://github.com/firefly-iii/firefly-iii/commit/e80d616ef4397e6e764f6b7b7a5b30121244933c'}
| null |
Packagist
|
GHSA-f99r-jjgr-f373
|
SQL injection in ImpressCMS
|
SQL Injection in ImpressCMS 1.4.3 and earlier allows remote attackers to inject into the code in unintended way, this allows an attacker to read and modify the sensitive information from the database used by the application. If misconfigured, an attacker can even upload a malicious web shell to compromise the entire system.
|
{'CVE-2022-26986'}
|
2022-04-18T22:23:05Z
|
2022-04-06T00:01:30Z
|
HIGH
| null |
{'CWE-89'}
|
{'https://github.com/ImpressCMS/impresscms', 'https://github.com/sartlabs/0days/blob/main/ImpressCMS1.4.3/Exploit.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26986'}
| null |
Packagist
|
GHSA-xwv6-v7qx-f5jc
|
Code injection in ezsystems/ezpublish-kernel
|
When image files are uploaded, they are made accessible under a name similar to the original file name. There are two issues with this. Both require access to uploading images in order to exploit them, this limits the impact. The first issue is that certain injection attacks can be possible, since not all possible attack vectors are removed from the original file name.
The second issue is that direct access to the images is not access controlled. This is by design, for performance reasons, and documented as such. But it does mean that images not meant to be publicly accessible can be accessed, provided that the image path and filename is correctly deduced and/or guessed, through dictionary attacks and similar.
|
{'CVE-2022-25337'}
|
2022-03-04T21:37:26Z
|
2022-02-19T00:01:25Z
|
CRITICAL
| null |
{'CWE-74'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-25337', 'https://github.com/ezsystems/ezpublish-kernel', 'https://developers.ibexa.co/security-advisories/ibexa-sa-2022-001-image-filenames-sanitization'}
| null |
Packagist
|
GHSA-rp42-c45j-g46x
|
yetiforcecrm is vulnerable to Cross-site Scripting
|
yetiforcecrm is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
|
{'CVE-2021-4107'}
|
2021-12-16T14:09:16Z
|
2021-12-16T14:12:23Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-4107', 'https://github.com/yetiforcecompany/yetiforcecrm', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/a062d3d5fecb000db207a2ad8a446db97ad96b89', 'https://huntr.dev/bounties/1d124520-cf29-4539-a0f3-6d041af7b5a8'}
| null |
Packagist
|
GHSA-9c5c-5j4h-8q2c
|
bookstack is vulnerable to Improper Access Control.
|
bookstack prior to version 21.11.3 is vulnerable to Improper Access Control.
|
{'CVE-2021-4119'}
|
2022-01-04T19:34:00Z
|
2021-12-16T19:40:26Z
|
MODERATE
| null |
{'CWE-284'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-4119', 'https://github.com/bookstackapp/bookstack/commit/e765e618547c92f4e0b46caca6fb91f0174efd99', 'https://huntr.dev/bounties/135f2d7d-ab0b-4351-99b9-889efac46fca', 'https://github.com/BookStackApp/BookStack/releases/tag/v21.11.3', 'https://github.com/bookstackapp/bookstack'}
| null |
Packagist
|
GHSA-284f-f2hw-j2gx
|
Server-Side Request Forgery vulnerability in concrete5
|
A Server-Side Request Forgery vulnerability was found in concrete5 < 8.5.5 that allowed a decimal notation encoded IP address to bypass the limitations in place for localhost allowing interaction with local services. Impact can vary depending on services exposed.
|
{'CVE-2021-22958'}
|
2021-10-18T18:15:50Z
|
2021-10-12T18:41:59Z
|
HIGH
| null |
{'CWE-918'}
|
{'https://github.com/concrete5/concrete5', 'https://github.com/concrete5/concrete5/pull/8826', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22958', 'https://hackerone.com/reports/863221', 'https://documentation.concretecms.org/developers/introduction/version-history/855-release-notes'}
| null |
Packagist
|
GHSA-pm77-c4q7-3fwj
|
Improper Certificate Validation in Heartland & Global Payments PHP SDK
|
Gateways/Gateway.php in Heartland & Global Payments PHP SDK before 2.0.0 does not enforce SSL certificate validations.
|
{'CVE-2019-20455'}
|
2021-10-08T22:58:55Z
|
2021-10-12T16:31:12Z
|
MODERATE
| null |
{'CWE-295'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-20455', 'https://github.com/globalpayments/php-sdk/releases/tag/2.0.0', 'https://winterdragon.ca/global-payments-vulnerability/', 'https://github.com/globalpayments/php-sdk/pull/8/commits/c86e18f28c5eba0d6ede7d557756d978ea83d3c9', 'https://github.com/globalpayments/php-sdk', 'https://github.com/globalpayments/php-sdk/compare/1.3.3...2.0.0', 'https://github.com/globalpayments/php-sdk/pull/8'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.