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 ⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA | GHSA-wcvp-r8j8-47pc | Double free in toodee | An issue was discovered in the toodee crate before 0.3.0 for Rust. Row insertion can cause a double free upon an iterator panic. | {'CVE-2021-28028'} | 2021-09-01T18:30:35Z | 2021-09-01T18:30:35Z | CRITICAL | 9.8 | {'CWE-415'} | {'https://rustsec.org/advisories/RUSTSEC-2021-0028.html', 'https://github.com/advisories/GHSA-wcvp-r8j8-47pc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28028'} | null |
GHSA | GHSA-3h29-52vh-pqgr | Uncontrolled Resource Consumption in Apache Tika | A carefully crafted or corrupt PSD file can cause excessive memory usage in Apache Tika's PSDParser in versions 1.0-1.23. | {'CVE-2020-1950'} | 2021-05-07T15:53:48Z | 2021-05-07T15:53:48Z | MODERATE | 5.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-3h29-52vh-pqgr', 'https://lists.apache.org/thread.html/r463b1a67817ae55fe022536edd6db34e8f9636971188430cbcf8a8dd%40%3Cdev.tika.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1950', 'https://usn.ubuntu.com/4564-1/', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00035.html'} | null |
GHSA | GHSA-rmr5-cpv2-vgjf | Denial of Service by injecting highly recursive collections or maps in XStream | ### Impact
The vulnerability may allow a remote attacker to allocate 100% CPU time on the target system depending on CPU type or parallel execution of such a payload resulting in a denial of service only by manipulating the processed input stream.
### Patches
XStream 1.4.19 monitors and accumulates the time it takes to add elements to collections and throws an exception if a set threshold is exceeded.
### Workarounds
The attack uses the hash code implementation for collections and maps to force an exponential calculation time due to highly recursive structures with in the collection or map. Following types of the Java runtime are affected in Java versions available in December 2021:
- java.util.HashMap
- java.util.HashSet
- java.util.Hashtable
- java.util.LinkedHashMap
- java.util.LinkedHashSet
- java.util.Stack (older Java revisions only)
- java.util.Vector (older Java revisions only)
- Other third party collection implementations that use their element's hash code may also be affected
If your object graph does not use referenced elements at all, you may simply set the NO_REFERENCE mode:
```Java
XStream xstream = new XStream();
xstream.setMode(XStream.NO_REFERENCES);
```
If your object graph contains neither a Hashtable, HashMap nor a HashSet (or one of the linked variants of it) then you can use the security framework to deny the usage of these types:
```Java
XStream xstream = new XStream();
xstream.denyTypes(new Class[]{
java.util.HashMap.class, java.util.HashSet.class, java.util.Hashtable.class, java.util.LinkedHashMap.class, java.util.LinkedHashSet.class
});
```
Unfortunately these types are very common. If you only use HashMap or HashSet and your XML refers these only as default map or set, you may additionally change the default implementation of java.util.Map and java.util.Set at unmarshalling time::
```Java
xstream.addDefaultImplementation(java.util.TreeMap.class, java.util.Map.class);
xstream.addDefaultImplementation(java.util.TreeSet.class, java.util.Set.class);
```
However, this implies that your application does not care about the implementation of the map and all elements are comparable.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-43859](https://x-stream.github.io/CVE-2021-43859.html).
### Credits
The vulnerability was discovered and reported by r00t4dm at Cloud-Penetrating Arrow Lab.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
| {'CVE-2021-43859'} | 2022-04-22T15:34:22Z | 2022-02-01T00:48:15Z | HIGH | 7.5 | {'CWE-400', 'CWE-502'} | {'https://lists.debian.org/debian-lts-announce/2022/02/msg00018.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-rmr5-cpv2-vgjf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VACQYG356OHUTD5WQGAQ4L2TTFTAV3SJ/', 'http://www.openwall.com/lists/oss-security/2022/02/09/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XODFRE2ZL64FICBJDOPWOLPTSSAI4U7X/', 'https://x-stream.github.io/CVE-2021-43859.html', 'https://github.com/x-stream/xstream/commit/e8e88621ba1c85ac3b8620337dd672e0c0c3a846', 'https://github.com/x-stream/xstream/security/advisories/GHSA-rmr5-cpv2-vgjf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43859'} | null |
GHSA | GHSA-rg3q-jxmp-pvjj | Low severity vulnerability that affects materialize-css | In Materialize through 1.0.0, XSS is possible via the Toast feature. | {'CVE-2019-11004'} | 2021-09-17T17:47:07Z | 2019-04-09T19:44:37Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-11004', 'https://github.com/Dogfalo/materialize/issues/6286', 'https://github.com/advisories/GHSA-rg3q-jxmp-pvjj'} | null |
GHSA | GHSA-qv78-398w-cxp7 | Malicious Package in shrugging-logging | All versions of `shrugging-logging` contain malicious code as a postinstall script. The package fetches all names of npm packages owned by the user and attempts to add another maintainer to every package as a means of package hijacking,
## Recommendation
Remove the package from your system. If you own any packages that were compromised please contact npm security immediately at security@npmjs.com. Also enable 2FA for publishing to further secure packages you maintain. | null | 2021-09-30T22:00:05Z | 2020-09-11T21:08:19Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://github.com/advisories/GHSA-qv78-398w-cxp7', 'https://www.npmjs.com/advisories/920'} | null |
GHSA | GHSA-r5mf-q76q-f2xq | Cross-site scripting in Centreon | Centreon version 20.10.2 is affected by a cross-site scripting (XSS) vulnerability. The dep_description (Dependency Description) and dep_name (Dependency Name) parameters are vulnerable to stored XSS. A user has to log in and go to the Configuration > Notifications > Hosts page. | {'CVE-2021-27676'} | 2021-06-08T20:13:05Z | 2021-06-08T20:13:05Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-r5mf-q76q-f2xq', 'https://github.com/centreon/centreon/pull/9587', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27676', 'http://centreon.com', 'https://github.com/centreon/centreon/releases/tag/20.10.7'} | null |
GHSA | GHSA-645p-88qh-w398 | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization. | {'CVE-2018-14718'} | 2021-06-11T15:54:20Z | 2019-01-04T19:06:55Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://www.debian.org/security/2019/dsa-4452', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44', 'https://nvd.nist.gov/vuln/detail/CVE-2018-14718', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://seclists.org/bugtraq/2019/May/68', 'https://lists.apache.org/thread.html/6a78f88716c3c57aa74ec05764a37ab3874769a347805903b393b286@%3Cdev.lucene.apache.org%3E', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.7', 'https://github.com/advisories/GHSA-645p-88qh-w398', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://lists.apache.org/thread.html/82b01bfb6787097427ce97cec6a7127e93718bc05d1efd5eaffc228f@%3Cdev.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'http://www.securityfocus.com/bid/106601', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://lists.apache.org/thread.html/ba973114605d936be276ee6ce09dfbdbf78aa56f6cdc6e79bfa7b8df@%3Cdev.lucene.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://access.redhat.com/errata/RHSA-2019:1823', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/FasterXML/jackson-databind/issues/2097', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/r1d4a247329a8478073163567bbc8c8cb6b49c6bfc2bf58153a857af1@%3Ccommits.druid.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://access.redhat.com/errata/RHSA-2019:1782'} | null |
GHSA | GHSA-rccq-j2m7-8fwr | Double-free in id-map | An issue was discovered in the id-map crate through 2021-02-26 for Rust. A double free can occur in remove_set upon a panic in a Drop impl. | {'CVE-2021-30457'} | 2021-08-25T20:55:14Z | 2021-08-25T20:55:14Z | CRITICAL | 9.8 | {'CWE-415'} | {'https://github.com/advisories/GHSA-rccq-j2m7-8fwr', 'https://github.com/andrewhickman/id-map/issues/3', 'https://rustsec.org/advisories/RUSTSEC-2021-0052.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30457'} | null |
GHSA | GHSA-87g3-x896-w798 | Downloads Resources over HTTP in atom-node-module-installer | Affected versions of `atom-node-module-installer` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `atom-node-module-installer`.
## Recommendation
No patch is currently available for this vulnerability, and the package has not been updated since 2014.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees. | {'CVE-2016-10620'} | 2021-01-08T19:11:38Z | 2019-02-18T23:56:53Z | HIGH | 0 | {'CWE-311'} | {'https://nodesecurity.io/advisories/216', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10620', 'https://github.com/advisories/GHSA-87g3-x896-w798', 'https://www.npmjs.com/advisories/216'} | null |
GHSA | GHSA-3x7h-5hfr-hvjm | Moderate severity vulnerability that affects io.undertow:undertow-core | It was found in Undertow before 1.3.28 that with non-clean TCP close, the Websocket server gets into infinite loop on every IO thread, effectively causing DoS. | {'CVE-2017-2670'} | 2021-08-31T21:36:40Z | 2018-10-19T16:54:56Z | MODERATE | 7.5 | {'CWE-835'} | {'https://github.com/advisories/GHSA-3x7h-5hfr-hvjm', 'https://nvd.nist.gov/vuln/detail/CVE-2017-2670'} | null |
GHSA | GHSA-wxj7-97fp-j53j | Exposure of Resource to Wrong Sphere in Zip-Local | The package zip-local before 0.3.5 are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) which can lead to an extraction of a crafted file outside the intended extraction directory. | {'CVE-2021-23484'} | 2022-02-07T21:20:29Z | 2022-02-01T00:46:01Z | CRITICAL | 9.8 | {'CWE-668', 'CWE-29'} | {'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085', 'https://github.com/advisories/GHSA-wxj7-97fp-j53j', 'https://snyk.io/vuln/SNYK-JS-ZIPLOCAL-2327477', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23484', 'https://github.com/Mostafa-Samir/zip-local/blob/master/main.js%23L365'} | null |
GHSA | GHSA-rpcg-f9q6-2mq6 | Remote Code Execution via traversal in TAL expressions | This advisory extends the previous advisory at https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36 with additional cases of TAL expression traversal vulnerabilities.
### Impact
Most Python modules are not available for using in TAL expressions that you can add through-the-web, for example in Zope Page Templates. This restriction avoids file system access, for example via the 'os' module. But some of the untrusted modules are available indirectly through Python modules that are available for direct use.
By default, you need to have the Manager role to add or edit Zope Page Templates through the web. Only sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk.
### Patches
The problem has been fixed in Zope 5.21 and 4.6.1.
### Workarounds
The workaround is the same as for https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36: A site administrator can restrict adding/editing Zope Page Templates through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing Zope Page Templates through the web should be restricted to trusted users only.
### References
* [The previous advisory (GHSA-5pr9-v234-jw36)](https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)
* Email us at [security@plone.org](mailto:security@plone.org)
| null | 2021-06-08T18:45:52Z | 2021-06-08T18:45:52Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/zopefoundation/Zope/security/advisories/GHSA-rpcg-f9q6-2mq6', 'https://github.com/advisories/GHSA-rpcg-f9q6-2mq6'} | null |
GHSA | GHSA-qv95-g3gm-x542 | Privilege Escalation in Hashicorp Vault | HashiCorp Vault and Vault Enterprise through 1.7.4 and 1.8.3 allowed a user with write permission to an entity alias ID sharing a mount accessor with another user to acquire this other user’s policies by merging their identities. Fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4. | {'CVE-2021-41802'} | 2021-10-20T17:39:35Z | 2021-10-12T16:39:01Z | MODERATE | 2.9 | {'CWE-732', 'CWE-269'} | {'https://discuss.hashicorp.com/t/hcsec-2021-27-vault-merging-multiple-entity-aliases-for-the-same-mount-may-allow-privilege-escalation/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41802', 'https://github.com/advisories/GHSA-qv95-g3gm-x542'} | null |
GHSA | GHSA-r5qj-cvf9-p85h | Code Injection in PyTorch Lightning | PyTorch Lightning version 1.5.10 and prior is vulnerable to code injection. There is currently a [patch](https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae) available, anticipated to be part of the `1.6.0` release. | {'CVE-2022-0845'} | 2022-03-18T21:16:06Z | 2022-03-06T00:00:16Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0845', 'https://github.com/PyTorchLightning/pytorch-lightning/pull/12212', 'https://github.com/advisories/GHSA-r5qj-cvf9-p85h', 'https://huntr.dev/bounties/a795bf93-c91e-4c79-aae8-f7d8bda92e2a', 'https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae'} | null |
GHSA | GHSA-f5cx-5wr3-5qrc | Reference binding to nullptr in boosted trees | ### Impact
An attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestGainsPerFeature(
node_id_range=[],
stats_summary_list=[[1,2,3]],
l1=[1.0],
l2=[1.0],
tree_complexity =[1.0],
min_node_weight =[1.17],
max_splits=5)
```
A similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestFeatureSplitV2(
node_id_range=[],
stats_summaries_list=[[1,2,3]],
split_types=[''],
candidate_feature_ids=[1,2,3,4],
l1=[1],
l2=[1],
tree_complexity=[1.0],
min_node_weight=[1.17],
logits_dimension=5)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values.
### Patches
We have patched the issue in GitHub commit [9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad](https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad) and in commit. [429f009d2b2c09028647dd4bb7b3f6f414bbaad7](https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37662'} | 2021-08-25T14:42:26Z | 2021-08-25T14:42:26Z | HIGH | 7.1 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f5cx-5wr3-5qrc', 'https://github.com/advisories/GHSA-f5cx-5wr3-5qrc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37662', 'https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7', 'https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad'} | null |
GHSA | GHSA-jhx3-2w5x-x39x | High severity vulnerability that affects Microsoft.ChakraCore | An information disclosure vulnerability exists when the scripting engine does not properly handle objects in memory in Microsoft Edge, aka 'Scripting Engine Information Disclosure Vulnerability'. | {'CVE-2019-0746'} | 2021-09-14T19:44:14Z | 2019-04-09T19:43:38Z | MODERATE | 6.5 | null | {'https://github.com/advisories/GHSA-jhx3-2w5x-x39x', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0746', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0746'} | null |
GHSA | GHSA-2p6r-37p9-89p2 | Authz Module Non-Determinism | ### Impact
Consensus failure for 0.43.x and 0.44.{0,1} users.
Funds and balances are safe.
### Patches
0.44.2
### Workarounds
Manually patch the code.
---
Full details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349. | {'CVE-2021-41135'} | 2022-04-19T19:03:11Z | 2021-10-21T17:46:57Z | MODERATE | 6.5 | {'CWE-754'} | {'https://github.com/advisories/GHSA-2p6r-37p9-89p2', 'https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349', 'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41135', 'https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-2p6r-37p9-89p2', 'https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.2'} | null |
GHSA | GHSA-wqr3-24xm-fxhq | Directory Traversal in wffserve | Affected versions of `wffserve` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead. | {'CVE-2017-16168'} | 2021-08-09T22:32:24Z | 2020-09-01T17:31:22Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-wqr3-24xm-fxhq', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/city-weather-abe', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/wffserve', 'https://www.npmjs.com/advisories/407', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16168'} | null |
GHSA | GHSA-j8qr-rvcv-crhv | Malicious Package in electron-native-notify | All versions of `electron-native-notify` contain malicious code. The package was part of a targeted attack to steal cryptocurrency wallet seeds and upload them to a remote server, effectively giving attackers access to users wallets.
## Recommendation
Remove the package from your environment and [follow the recommendations by Komodo](https://komodoplatform.com/vulnerability-discovered-in-komodos-agama-wallet-this-is-what-you-need-to-do/) | null | 2020-09-11T21:18:05Z | 2020-09-11T21:18:05Z | CRITICAL | 0 | null | {'https://github.com/advisories/GHSA-j8qr-rvcv-crhv', 'https://komodoplatform.com/vulnerability-discovered-in-komodos-agama-wallet-this-is-what-you-need-to-do/', 'https://blog.npmjs.org/post/185397814280/plot-to-steal-cryptocurrency-foiled-by-the-npm', 'https://www.npmjs.com/advisories/927'} | null |
GHSA | GHSA-6mh3-j5r5-2379 | Cross-Site Scripting in Query Generator & Query View | > ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (4.5)
### Problem
Failing to properly encode error messages, the components _QueryGenerator_ and _QueryView_ are vulnerable to both reflected and persistent cross-site scripting. A valid backend user account having administrator privileges is needed to exploit this vulnerability.
### Solution
Update to TYPO3 versions 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.
### Credits
Thanks to Richie Lee who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-010](https://typo3.org/security/advisory/typo3-core-sa-2021-010) | {'CVE-2021-32668'} | 2022-04-19T19:02:59Z | 2021-07-22T19:36:58Z | MODERATE | 6.4 | {'CWE-79'} | {'https://github.com/TYPO3/typo3/security/advisories/GHSA-6mh3-j5r5-2379', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32668', 'https://typo3.org/security/advisory/typo3-core-sa-2021-010', 'https://github.com/advisories/GHSA-6mh3-j5r5-2379', 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-6mh3-j5r5-2379'} | null |
GHSA | GHSA-r4pj-74mg-8868 | Division by 0 in `Conv2DBackpropFilter` | ### Impact
An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropFilter`:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 0, 1, 0], dtype=tf.float32)
filter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)
out_backprop = tf.constant([], shape=[0, 0, 1, 1], dtype=tf.float32)
tf.raw_ops.Conv2DBackpropFilter(input=input_tensor, filter_sizes=filter_sizes,
out_backprop=out_backprop,
strides=[1, 66, 18, 1], use_cudnn_on_gpu=True,
padding='SAME', explicit_paddings=[],
data_format='NHWC', dilations=[1, 1, 1, 1])
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/496c2630e51c1a478f095b084329acedb253db6b/tensorflow/core/kernels/conv_grad_shape_utils.cc#L130) does a modulus operation where the divisor is controlled by the caller:
```cc
if (dims->in_depth % filter_shape.dim_size(num_dims - 2)) { ... }
```
### Patches
We have patched the issue in GitHub commit [fca9874a9b42a2134f907d2fb46ab774a831404a](https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29524'} | 2021-05-21T14:21:47Z | 2021-05-21T14:21:47Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r4pj-74mg-8868', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29524', 'https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a', 'https://github.com/advisories/GHSA-r4pj-74mg-8868'} | null |
GHSA | GHSA-fmqw-vqh5-cwq9 | Apache NiFi user log out issue | When using an authentication mechanism other than PKI, when the user clicks Log Out in NiFi versions 1.0.0 to 1.9.2, NiFi invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi. | {'CVE-2019-12421'} | 2021-08-19T16:03:17Z | 2019-12-02T18:19:39Z | HIGH | 8.8 | {'CWE-613'} | {'https://github.com/advisories/GHSA-fmqw-vqh5-cwq9', 'https://github.com/apache/nifi/pull/3362', 'https://nifi.apache.org/security.html#CVE-2019-12421', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12421', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E'} | null |
GHSA | GHSA-98j8-c9q4-r38g | Memory exhaustion in Tensorflow | ### Impact
The [implementation of `StringNGrams`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/string_ngrams_op.cc#L29-L161) can be used to trigger a denial of service attack by causing an OOM condition after an integer overflow:
```python
import tensorflow as tf
tf.raw_ops.StringNGrams(
data=['123456'],
data_splits=[0,1],
separator='a'*15,
ngram_widths=[],
left_pad='',
right_pad='',
pad_width=-5,
preserve_short_sequences=True)
```
We are missing a validation on `pad_witdh` and that result in computing a negative value for `ngram_width` which is later used to allocate parts of the output.
### Patches
We have patched the issue in GitHub commit [f68fdab93fb7f4ddb4eb438c8fe052753c9413e8](https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team. | {'CVE-2022-21733'} | 2022-02-11T17:04:39Z | 2022-02-10T00:20:51Z | MODERATE | 4.3 | {'CWE-400', 'CWE-190'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21733', 'https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8', 'https://github.com/advisories/GHSA-98j8-c9q4-r38g', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/string_ngrams_op.cc#L29-L161'} | null |
GHSA | GHSA-64rh-r86q-75ff | Hard coded cryptographic key in Kiali | A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1764'} | 2021-05-18T18:28:59Z | 2021-05-18T18:28:59Z | HIGH | 8.6 | {'CWE-798', 'CWE-321'} | {'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/jpts/cve-2020-1764-poc', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1764', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810383', 'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1764', 'https://github.com/advisories/GHSA-64rh-r86q-75ff', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f'} | null |
GHSA | GHSA-74w3-2r77-fw5h | Use of Externally-Controlled Format String in consoleme | A Python format string issue leading to information disclosure and potentially remote code execution in ConsoleMe for all versions prior to 1.2.2 | {'CVE-2022-27177'} | 2022-04-18T22:21:19Z | 2022-04-03T00:00:58Z | CRITICAL | 9.8 | {'CWE-134'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-27177', 'https://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2022-001.md', 'https://github.com/advisories/GHSA-74w3-2r77-fw5h'} | null |
GHSA | GHSA-w5gh-2wr2-pm6g | Denial of Service in Tensorflow | ### Impact
Changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using `tensorflow-serving` or other inference-as-a-service installments.
We have added fixes to this in f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d (both going into TensorFlow 2.2.0 and 2.3.0 but not yet backported to earlier versions). However, this was not enough, as #41097 reports a different failure mode.
### Patches
We have patched the issue in adf095206f25471e864a8e63a0f1caef53a0e3a6 and will release patch releases for all versions between 1.15 and 2.3. Patch releases for versions between 1.15 and 2.1 will also contain cherry-picks of f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Shuaike Dong, from Alipay Tian Qian Security Lab && Lab for Applied Security Research, CUHK. | {'CVE-2020-15206'} | 2021-08-26T15:16:58Z | 2020-09-25T18:28:40Z | CRITICAL | 9 | {'CWE-20'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/commit/f760f88b4267d981e13f4b302c437ae800445968', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w5gh-2wr2-pm6g', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15206', 'https://github.com/tensorflow/tensorflow/commit/fcfef195637c6e365577829c4d67681695956e7d', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/advisories/GHSA-w5gh-2wr2-pm6g', 'https://github.com/tensorflow/tensorflow/commit/adf095206f25471e864a8e63a0f1caef53a0e3a6'} | null |
GHSA | GHSA-9h4h-8w5p-f28w | Denial of Service in geth | cmd/evm/runner.go in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode. | {'CVE-2018-19184'} | 2021-06-29T21:23:15Z | 2021-06-29T21:23:15Z | HIGH | 7.5 | {'CWE-476'} | {'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19184', 'https://github.com/ethereum/go-ethereum/issues/18069', 'https://github.com/advisories/GHSA-9h4h-8w5p-f28w', 'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef'} | null |
GHSA | GHSA-m429-fhmv-c6q2 | Improper Verification of Cryptographic Signature | A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability. | {'CVE-2020-14365'} | 2022-04-07T15:10:46Z | 2021-04-20T16:44:07Z | HIGH | 7.1 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-14365', 'https://www.debian.org/security/2021/dsa-4950', 'https://github.com/advisories/GHSA-m429-fhmv-c6q2', 'https://bugzilla.redhat.com/show_bug.cgi?id=1869154'} | null |
GHSA | GHSA-4jfq-q299-g4cr | Malicious Package in reqquest | All versions of `reqquest` typosquatted a popular package of similar name and tracked users who had installed the incorrect package. The package uploaded information to a remote server including: name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo. There is no further compromise.
## Recommendation
Remove the package from your dependencies and always ensure package names are typed correctly upon installation. | null | 2021-10-01T14:06:36Z | 2020-09-02T20:28:57Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://github.com/advisories/GHSA-4jfq-q299-g4cr', 'https://www.npmjs.com/advisories/860'} | null |
GHSA | GHSA-f9pg-g9xw-r5g2 | SQL Injection in Jeecg-boot | Jeecg-boot v3.0 was discovered to contain a SQL injection vulnerability via the code parameter in /sys/user/queryUserComponentData. | {'CVE-2022-22881'} | 2022-02-26T00:52:07Z | 2022-02-17T00:00:25Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/advisories/GHSA-f9pg-g9xw-r5g2', 'https://github.com/jeecgboot/jeecg-boot/issues/3348', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22881'} | null |
GHSA | GHSA-cxwc-8pqp-2whw | Directory Traversal in qinserve | Affected versions of `qinserve` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead. | {'CVE-2017-16197'} | 2021-01-14T15:41:10Z | 2020-09-01T18:20:40Z | HIGH | 0 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-16197', 'https://github.com/advisories/GHSA-cxwc-8pqp-2whw', 'https://www.npmjs.com/advisories/434', 'https://nodesecurity.io/advisories/434', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/qinserve'} | null |
GHSA | GHSA-rvj9-8cvx-3vq9 | Invalid Curve Attack in node-jose | Affected versions of `node-jose` are vulnerable to an invalid curve attack. This allows an attacker to recover the private secret key when JWE with Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static (ECDH-ES) is used.
[Proof of Concept](https://gist.github.com/asanso/fa25685348051ef6a28d49aa0f27a4ae)
## Recommendation
Update to version 0.9.3 or later. | {'CVE-2017-16007'} | 2021-01-08T01:57:52Z | 2018-07-20T21:10:14Z | HIGH | 0 | {'CWE-200'} | {'https://nodesecurity.io/advisories/324', 'https://github.com/cisco/node-jose', 'https://github.com/advisories/GHSA-rvj9-8cvx-3vq9', 'https://www.npmjs.com/advisories/324', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16007', 'https://gist.github.com/asanso/fa25685348051ef6a28d49aa0f27a4ae', 'http://blog.intothesymmetry.com/2017/03/critical-vulnerability-in-json-web.html'} | null |
GHSA | GHSA-c5f8-35qr-q4fm | HTML injection in email and account expiry notifications | ### Impact
The notification emails sent for notifications for missed messages or for an expiring account are subject to HTML injection. In the case of the notification for missed messages, this could allow an attacker to insert forged content into the email.
The account expiry feature is not enabled by default and the HTML injection is not controllable by an attacker.
### Patches
This issue is fixed in #9200.
### Workarounds
For the missed messages notifications:
The `notif.html`, `notif_mail.html`, and `room.html` templates can be overridden with custom templates that manually escapes the variables using [JInja2's `escape` filter](https://jinja.palletsprojects.com/en/2.11.x/templates/#escape). See the `email.template_dir` setting.
For the account expiry notifications:
1. Account expiry can be disabled via the `account_validity.enabled` setting.
2. The `notice_expiry.html` template can be overridden with a custom template that manually escapes the variables using [JInja2's `escape` filter](https://jinja.palletsprojects.com/en/2.11.x/templates/#escape). See the `email.template_dir` setting. | {'CVE-2021-21333'} | 2021-08-31T21:07:09Z | 2021-03-26T19:53:04Z | MODERATE | 6.1 | {'CWE-74'} | {'https://github.com/advisories/GHSA-c5f8-35qr-q4fm', 'https://github.com/matrix-org/synapse/releases/tag/v1.27.0', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNNAJOZNMVMXM6AS7RFFKB4QLUJ4IFEY/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21333', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-c5f8-35qr-q4fm', 'https://github.com/matrix-org/synapse/pull/9200', 'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df'} | null |
GHSA | GHSA-3hjg-vc7r-rcrw | Denial of Service vulnerability in @podium/layout and @podium/proxy | ### Impact
An attacker using the `Trailer` header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.
### Patches
`@podium/layout` which is the main way developers/users are vulnerable to this exploit, has been patched in version `4.6.110`. All earlier versions are vulnerable.
`@podium/proxy` which is the source of the vulnerability and is used by `@podium/layout` has been patched in version `4.2.74`. All earlier versions are vulnerable.
### Workarounds
It is not easily possible to work around this issue without upgrading. We recommend upgrading `@podium/layout` and/or `@podium/proxy` as soon as possible.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [podium-lib/issues](https://github.com/podium-lib/issues)
### Credits
The vulnerability was reported by [krynos](https://hackerone.com/krynos) from [Ercoli Consulting](https://www.ercoliconsulting.eu/) via FINN.no's private bug bounty program
| {'CVE-2022-24822'} | 2022-04-12T21:50:50Z | 2022-04-07T15:20:23Z | HIGH | 7.5 | {'CWE-248'} | {'https://github.com/advisories/GHSA-3hjg-vc7r-rcrw', 'https://github.com/podium-lib/layout/releases/tag/v4.6.110', 'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24822', 'https://github.com/podium-lib/proxy/releases/tag/v4.2.74', 'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039', 'https://github.com/podium-lib/proxy/security/advisories/GHSA-3hjg-vc7r-rcrw'} | null |
GHSA | GHSA-6cpc-mj5c-m9rq | Arbitrary File Write in cli | Affected versions of `cli` use predictable temporary file names. If an attacker can create a symbolic link at the location of one of these temporarly file names, the attacker can arbitrarily write to any file that the user which owns the `cli` process has permission to write to.
## Proof of Concept
By creating Symbolic Links at the following locations, the target of the link can be written to.
```
lock_file = '/tmp/' + cli.app + '.pid',
log_file = '/tmp/' + cli.app + '.log';
```
## Recommendation
Update to version 1.0.0 or later. | {'CVE-2016-10538'} | 2021-01-08T19:45:50Z | 2019-02-18T23:40:03Z | LOW | 0 | {'CWE-22'} | {'https://nodesecurity.io/advisories/95', 'https://github.com/advisories/GHSA-6cpc-mj5c-m9rq', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809252', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10538', 'https://github.com/node-js-libs/cli/issues/81', 'https://www.npmjs.com/advisories/95'} | null |
GHSA | GHSA-crpm-fm48-chj7 | SQL Injection in resquel | All versions of `resquel` are vulnerable to SQL Injection. Query parameters are not properly sanitized, allowing attackers to inject SQL statements and execute arbitrary SQL queries
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2021-09-28T16:52:04Z | 2020-09-11T21:13:44Z | HIGH | 0 | {'CWE-89'} | {'https://github.com/advisories/GHSA-crpm-fm48-chj7', 'https://www.npmjs.com/advisories/963'} | null |
GHSA | GHSA-fwvq-x4j9-hr5f | Malicious Package in bs58chekc | All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | null | 2021-10-01T20:50:01Z | 2020-09-03T19:43:09Z | CRITICAL | 9.1 | {'CWE-506'} | {'https://www.npmjs.com/advisories/1377', 'https://github.com/advisories/GHSA-fwvq-x4j9-hr5f'} | null |
GHSA | GHSA-x67x-98x7-wv26 | OS Command Injection in gulp-tape | gulp-tape through 1.0.0 allows execution of arbitrary commands. It is possible to inject arbitrary commands as part of 'gulp-tape' options. | {'CVE-2020-7605'} | 2021-07-28T21:17:57Z | 2021-05-07T16:14:56Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7605', 'https://github.com/advisories/GHSA-x67x-98x7-wv26', 'https://snyk.io/vuln/SNYK-JS-GULPTAPE-560124'} | null |
GHSA | GHSA-cx2r-mf6x-55rx | Stored XSS with custom URLs in PrestaShop module ps_linklist | ### Impact
Stored XSS when using custom URLs.
### Patches
The problem is fixed in 3.1.0
### References
[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html) | {'CVE-2020-5273'} | 2021-10-12T16:01:36Z | 2021-10-12T16:01:36Z | MODERATE | 4.1 | {'CWE-79'} | {'https://github.com/PrestaShop/ps_linklist/commit/83e6e0bdda2287f4d6e64127cb90c41d26b5ad82', 'https://github.com/advisories/GHSA-cx2r-mf6x-55rx', 'https://github.com/PrestaShop/ps_linklist/security/advisories/GHSA-cx2r-mf6x-55rx', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5273'} | null |
GHSA | GHSA-934w-hvj4-7fr6 | Path Traversal in jsreport-chrome-pdf | This affects the package jsreport-chrome-pdf before 1.10.0. | {'CVE-2020-7762'} | 2021-08-02T15:38:02Z | 2021-04-13T15:25:15Z | MODERATE | 6.5 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7762', 'https://snyk.io/vuln/SNYK-JS-JSREPORTCHROMEPDF-1037310', 'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2', 'https://github.com/advisories/GHSA-934w-hvj4-7fr6'} | null |
GHSA | GHSA-f8mr-jv2c-v8mg | Invalid root may become trusted root in The Update Framework (TUF) | ### Impact
The Python TUF reference implementation `tuf<0.12` will incorrectly trust a previously downloaded root metadata file which failed verification at download time. This allows an attacker who is able to serve multiple new versions of root metadata (i.e. by a man-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates.
While investigating the reported vulnerability, we discovered that the detailed client workflow was not fully implemented. Specifically, for step 1.3 the newly downloaded root metadata was not being verified with a threshold of keys specified in the new root metadata file.
This missing step of the client workflow has been implemented in [PR #1101](https://github.com/theupdateframework/tuf/pull/1101), which is included in [v0.14.0](https://github.com/theupdateframework/tuf/releases/tag/v0.14.0) of tuf.
### Patches
A [fix](https://github.com/theupdateframework/tuf/pull/885), is available in version [0.12](https://github.com/theupdateframework/tuf/releases/tag/v0.12.0) and newer.
### Workarounds
No workarounds are known for this issue.
### References
* Pull request resolving the invalid root becoming trusted issue [PR 885](https://github.com/theupdateframework/tuf/pull/885)
* Pull request implementing self verification of newly downloaded root metadata [PR 1101](https://github.com/theupdateframework/tuf/pull/1101) | {'CVE-2020-15163'} | 2022-04-19T19:02:30Z | 2020-09-09T17:29:27Z | HIGH | 8.7 | {'CWE-863', 'CWE-345'} | {'https://github.com/theupdateframework/tuf/releases/tag/v0.12.0', 'https://github.com/theupdateframework/tuf/pull/885', 'https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15163', 'https://github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg', 'https://pypi.org/project/tuf', 'https://github.com/advisories/GHSA-f8mr-jv2c-v8mg'} | null |
GHSA | GHSA-vxfp-qmpq-6826 | Malicious Package in hpmm | All versions of `hpmm` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | null | 2021-09-30T19:46:36Z | 2020-09-03T17:38:09Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://github.com/advisories/GHSA-vxfp-qmpq-6826', 'https://www.npmjs.com/advisories/1053'} | null |
GHSA | GHSA-m489-xr35-fjxr | Regular Expression Denial of Service in millisecond | Versions of `millisecond` prior to 0.1.2 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.
## Proof of concept
```
var ms = require('millisecond');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
ms(genstr(process.argv[2], "5") + " minutea");
```
## Recommendation
Update to version 0.1.2 or later. | null | 2021-09-22T20:35:08Z | 2021-09-22T20:35:08Z | MODERATE | 0 | {'CWE-400', 'CWE-1333'} | {'https://github.com/unshiftio/millisecond/pull/4', 'https://github.com/advisories/GHSA-m489-xr35-fjxr', 'https://www.npmjs.com/advisories/59'} | null |
GHSA | GHSA-h563-xh25-x54q | Workflow re-write vulnerability using input parameter | ### Impact
* Allow end-users to set input parameters, but otherwise expect workflows to be secure.
### Patches
Not yet.
### Workarounds
* Set `EXPRESSION_TEMPLATES=false` for the workflow controller
### References
* https://github.com/argoproj/argo-workflows/issues/6441
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
| {'CVE-2021-37914'} | 2021-08-30T23:23:12Z | 2021-08-09T20:37:50Z | MODERATE | 0 | {'CWE-20'} | {'https://github.com/argoproj/argo-workflows/pull/6285', 'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1', 'https://github.com/argoproj/argo-workflows/pull/6442', 'https://github.com/advisories/GHSA-h563-xh25-x54q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37914', 'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54q', 'https://github.com/argoproj/argo-workflows/issues/6441'} | null |
GHSA | GHSA-3r3g-g73x-g593 | Improper Verification of Cryptographic Signature in coreos | ### Impact
coreos-installer fails to correctly verify GPG signatures when decompressing gzip-compressed artifacts. This allows bypass of signature verification in cases where coreos-installer decompresses a downloaded OS image, allowing an attacker who can modify the OS image to compromise a newly-installed system.
Default installations from ISO or PXE media in Fedora CoreOS, RHEL CoreOS, and RHEL for Edge are **not** affected, as coreos-installer installs from an OS image shipped as part of the install media.
These flows are affected:
1. Installing with `--image-file`, `--image-url`, or `coreos.inst.image_url`. For example, if a user has a local mirror of installation images, an attacker could replace an image with a gzip-compressed alternative (even if the file extension is `.xz`). The result:
```
$ coreos-installer install --image-url http://localhost:8080/image.xz /dev/loop0
Downloading image from http://localhost:8080/image.xz
Downloading signature from http://localhost:8080/image.xz.sig
> Read disk 749.9 MiB/749.9 MiB (100%)
gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT
gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39
gpg: BAD signature from "Fedora (34) <fedora-34-primary@fedoraproject.org>" [ultimate]
Install complete.
```
Notice that GPG reports a bad signature, but coreos-installer continues anyway. Automation that relies on coreos-installer's exit status will not notice either.
2. `coreos-installer download --decompress --image-url`:
```
$ coreos-installer download --decompress --image-url http://localhost:8080/image.xz
> Read disk 749.9 MiB/749.9 MiB (100%)
gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT
gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39
gpg: BAD signature from "Fedora (34) <fedora-34-primary@fedoraproject.org>" [ultimate]
./image
```
Again, coreos-installer reports success.
3. Installing with default parameters, when **not** installing from the image built into live ISO or PXE media, if the hosting service is compromised or if an active attacker gains control of the HTTPS response.
4. `coreos-installer download --decompress` if the hosting service is compromised or if an active attacker gains control of the HTTPS response.
### Patches
The vulnerability is [fixed](https://github.com/coreos/coreos-installer/pull/659) in coreos-installer 0.10.1.
### Workarounds
For `coreos-installer download`, do not use the `-d` or `--decompress` options.
For `coreos-installer install`, manually inspect the stderr output. If `BAD signature` appears, do not boot from the target disk. Note, however, that some OS services may have already accessed data on the compromised disk.
### References
For more information, see [PR 655](https://github.com/coreos/coreos-installer/pull/655).
### For more information
If you have any questions or comments about this advisory, [open an issue in coreos-installer](https://github.com/coreos/coreos-installer/issues/new/choose) or email the CoreOS [development mailing list](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/). | {'CVE-2021-20319'} | 2022-04-19T19:03:12Z | 2021-10-12T16:06:47Z | HIGH | 7.8 | {'CWE-347'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2011862', 'https://github.com/coreos/coreos-installer/security/advisories/GHSA-3r3g-g73x-g593', 'https://github.com/advisories/GHSA-3r3g-g73x-g593', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20319', 'https://github.com/coreos/coreos-installer/pull/655', 'https://github.com/coreos/coreos-installer/pull/659/commits/ad243c6f0eff2835b2da56ca5f7f33af76253c89'} | null |
GHSA | GHSA-rwv7-3v45-hg29 | Out-of-bounds Read | An issue was discovered in Pillow before 8.2.0. There is an out-of-bounds read in J2kDecode, in j2ku_gray_i. This dates to Pillow 2.4.0. | {'CVE-2021-25288'} | 2022-03-03T21:46:05Z | 2021-06-08T18:49:28Z | CRITICAL | 9.1 | {'CWE-125'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25288', 'https://security.gentoo.org/glsa/202107-33', 'https://github.com/python-pillow/Pillow/pull/5377#issuecomment-833821470', 'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode', 'https://github.com/advisories/GHSA-rwv7-3v45-hg29'} | null |
GHSA | GHSA-wp77-4gmm-7cq8 | Incorrect validation of `SaveV2` inputs | ### Impact
The code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference:
```python
import tensorflow as tf
tf.raw_ops.SaveV2(
prefix=['tensorflow'],
tensor_name=['v'],
shape_and_slices=[],
tensors=[1,2,3])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above.
However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation.
### Patches
We have patched the issue in GitHub commit [9728c60e136912a12d99ca56e106b7cce7af5986](https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37648'} | 2021-08-25T14:43:29Z | 2021-08-25T14:43:29Z | HIGH | 7.8 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wp77-4gmm-7cq8', 'https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986', 'https://github.com/advisories/GHSA-wp77-4gmm-7cq8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37648'} | null |
GHSA | GHSA-h6fg-mjxg-hqq4 | Integer truncation in Shard API usage | ### Impact
The `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/util/work_sharder.h#L59-L60
However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L204-L205
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L317-L318
In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.
### Patches
We have patched the issue in 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575. We will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15202'} | 2021-08-26T15:14:00Z | 2020-09-25T18:28:35Z | CRITICAL | 9 | {'CWE-754', 'CWE-197'} | {'https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575', 'https://github.com/advisories/GHSA-h6fg-mjxg-hqq4', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4', 'https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15202'} | null |
GHSA | GHSA-3v7g-4pg3-7r6j | OS Command injection in Apache Airflow | In Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI. | {'CVE-2022-24288'} | 2022-03-07T13:39:12Z | 2022-02-26T00:00:44Z | HIGH | 8.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-3v7g-4pg3-7r6j', 'https://lists.apache.org/thread/dbw5ozcmr0h0lhs0yjph7xdc64oht23t', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24288'} | null |
GHSA | GHSA-pm3v-qxf6-fgxv | Cross-site Scripting in pimcore | Cross-site Scripting (XSS) - Stored in Packagist pimcore/pimcore prior to 10.2.9. | {'CVE-2022-0285'} | 2022-01-27T18:32:20Z | 2022-01-21T18:08:43Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0285', 'https://github.com/advisories/GHSA-pm3v-qxf6-fgxv', 'https://github.com/pimcore/pimcore/commit/b432225952e2a5ab0268f401b85a14480369b835', 'https://huntr.dev/bounties/321918b2-aa01-410e-9f7c-dca5f286bc9c'} | null |
GHSA | GHSA-4vvg-x86p-mvqc | Leaking of user information on Cross-Domain communication in sysend | ### Impact
Users that use Cross-Origin communication and send sensitive information make it possible for this data to be intercepted.
This is not a big impact because it happens only on the same browser.
### Patches
It has been patched in version 1.10.0
### Workarounds
The only workaround is to not send sensitive information with sysend messages.
| {'CVE-2022-24762'} | 2022-03-28T17:26:42Z | 2022-03-14T22:43:23Z | MODERATE | 6.5 | {'CWE-200'} | {'https://github.com/jcubic/sysend.js/releases/tag/1.10.0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24762', 'https://github.com/jcubic/sysend.js/security/advisories/GHSA-4vvg-x86p-mvqc', 'https://github.com/jcubic/sysend.js/issues/33', 'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a', 'https://github.com/advisories/GHSA-4vvg-x86p-mvqc'} | null |
GHSA | GHSA-h8q5-g2cj-qr5h | Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack | In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing. However, Tika reuses SAXParsers and calls reset() after each parse, which, for Xerces2 parsers, as per the documentation, removes the user-specified SecurityManager and thus removes entity expansion limits after the first parse. Apache Tika versions from 0.1 to 1.19 are therefore still vulnerable to entity expansions which can lead to a denial of service attack. Users should upgrade to 1.19.1 or later. | {'CVE-2018-11796'} | 2022-04-26T21:46:05Z | 2018-10-17T15:43:25Z | HIGH | 7.5 | {'CWE-611'} | {'https://lists.apache.org/thread.html/88de8350cda9b184888ec294c813c5bd8a2081de8fd3666f8904bc05@%3Cdev.tika.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2018-11796', 'http://www.securityfocus.com/bid/105585', 'https://security.netapp.com/advisory/ntap-20190903-0002/', 'https://github.com/advisories/GHSA-h8q5-g2cj-qr5h', 'https://access.redhat.com/errata/RHSA-2019:3892'} | null |
GHSA | GHSA-3f95-w5h5-fq86 | Prototype Pollution in mergify | All versions of `mergify` are vulnerable to Prototype Pollution. The `mergify()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.
## Recommendation
No fix is currently available. Consider using an alternative module as the package is deprecated. | null | 2021-09-28T17:04:02Z | 2020-09-11T21:22:24Z | MODERATE | 0 | {'CWE-1321'} | {'https://hackerone.com/reports/439098', 'https://www.npmjs.com/advisories/995', 'https://github.com/advisories/GHSA-3f95-w5h5-fq86'} | null |
GHSA | GHSA-926x-m6m5-3mmp | OS Command Injection | push-dir through 0.4.1 allows execution of arbritary commands. Arguments provided as part of the variable "opt.branch" is not validated before being provided to the "git" command within "index.js#L139". This could be abused by an attacker to inject arbitrary commands. | {'CVE-2019-10803'} | 2022-02-09T22:50:06Z | 2022-02-09T22:50:06Z | HIGH | 9.8 | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-JS-PUSHDIR-559009', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10803', 'https://github.com/advisories/GHSA-926x-m6m5-3mmp', 'https://github.com/L33T-KR3W/push-dir/blob/master/index.js#L139'} | null |
GHSA | GHSA-w37c-q653-qg95 | Moderate severity vulnerability that affects actionpack | Cross-site scripting (XSS) vulnerability in the simple_format helper in actionpack/lib/action_view/helpers/text_helper.rb in Ruby on Rails 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via a crafted HTML attribute. | {'CVE-2013-6416'} | 2021-09-20T22:33:37Z | 2017-10-24T18:33:36Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-w37c-q653-qg95', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/5ZI1-H5OoIM/ZNq4FoR2GnIJ', 'http://weblog.rubyonrails.org/2013/12/3/Rails_3_2_16_and_4_0_2_have_been_released/', 'http://www.securityfocus.com/bid/64071', 'https://nvd.nist.gov/vuln/detail/CVE-2013-6416'} | null |
GHSA | GHSA-c497-v8pv-ch6x | Prototype pollution in nested-object-assign | The package nested-object-assign before 1.0.4 is vulnerable to Prototype Pollution via the default function. | {'CVE-2021-23329'} | 2021-02-01T15:01:14Z | 2021-02-01T15:01:14Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/Geta/NestedObjectAssign/pull/11', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23329', 'https://www.npmjs.com/package/nested-object-assign', 'https://github.com/advisories/GHSA-c497-v8pv-ch6x', 'https://snyk.io/vuln/SNYK-JS-NESTEDOBJECTASSIGN-1065977'} | null |
GHSA | GHSA-6hv3-7c34-4hx8 | Information Exposure Through Environmental Variables | In Nomad before version 0.9.5, when rendering a task template, all environment variables were available to the rendering task. As a fix, only task environment variables are used. | {'CVE-2019-14802'} | 2022-04-12T22:02:18Z | 2022-02-15T01:57:18Z | HIGH | 3.1 | {'CWE-526'} | {'https://github.com/hashicorp/nomad/pull/6055', 'https://github.com/advisories/GHSA-6hv3-7c34-4hx8', 'https://github.com/hashicorp/nomad/releases/tag/v0.9.5', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14802'} | null |
GHSA | GHSA-74hv-qjjq-h7g5 | datasette-graphql leaks details of the schema of private database files | ### Impact
When running against a Datasette instance with private databases, `datasette-graphql` would expose the schema of those database tables - but not the table contents.
### Patches
Patched in version 1.2.
### Workarounds
This issue is only present if a Datasette instance that includes private databases and has the `datasette-graphql` plugin installed is available on the public internet. Uninstalling the `datasette-graphql` plugin or preventing public access to the instance can workaround this issue.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [datasette-graphql](https://github.com/simonw/datasette-graphql)
* Contact [@simonw](https://twitter.com/simonw) by Twitter direct message | null | 2020-11-24T22:59:08Z | 2020-11-24T22:59:08Z | LOW | 0 | {'CWE-200'} | {'https://pypi.org/project/datasette-graphql/', 'https://github.com/simonw/datasette-graphql/security/advisories/GHSA-74hv-qjjq-h7g5', 'https://github.com/advisories/GHSA-74hv-qjjq-h7g5'} | null |
GHSA | GHSA-5g4r-87v2-jqvx | Downloads Resources over HTTP in apk-parser | apk-parser is a tool to extract Android Manifest info from an APK file.
apk-parser versions below 0.1.6 download binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
## Recommendation
Update to version 0.1.6 or later. | {'CVE-2016-10564'} | 2021-01-07T23:32:35Z | 2020-09-01T16:05:44Z | HIGH | 0 | {'CWE-311'} | {'https://github.com/advisories/GHSA-5g4r-87v2-jqvx', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10564', 'https://www.npmjs.com/advisories/195', 'https://nodesecurity.io/advisories/195'} | null |
GHSA | GHSA-3w6p-8f82-gw8r | Using JMSAppender in log4j configuration may lead to deserialization of untrusted data | ### Impact
ClickHouse JDBC Bridge uses [slf4j-log4j12 1.7.32](https://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.7.32/), which depends on [log4j 1.2.17](https://repo1.maven.org/maven2/log4j/log4j/1.2.17/). It allows a remote attacker to execute code on the server, if you changed default log4j configuration by adding JMSAppender and an insecure JMS broker.
### Patches
The patch version `2.0.7` removed log4j dependency by replacing `slf4j-log4j12` to `slf4j-jdk14`. Logging configuration is also changed from `log4j.properties` to `logging.properties`.
### Workarounds
1. Do NOT change log4j configuration to use JMSAppender along with insecure JMS broker
2. Alternatively, you can issue below command to remove `JMSAppender.class`:
```(bash)
# install zip command if you don't have
apt-get update && apt-get install -y zip
# remove the class
zip -d clickhouse-jdbc-bridge*.jar ru/yandex/clickhouse/jdbcbridge/internal/log4j/net/JMSAppender.class
```
### References
Please refer to [CVE-2021-4104](https://access.redhat.com/security/cve/CVE-2021-4104) to read more.
### For more information
If you have any questions or comments about this advisory, please feel free to open an issue in the repository.
| null | 2021-12-17T20:42:38Z | 2021-12-17T20:42:38Z | HIGH | 8.1 | {'CWE-502'} | {'https://access.redhat.com/security/cve/CVE-2021-4104', 'https://github.com/advisories/GHSA-3w6p-8f82-gw8r', 'https://github.com/ClickHouse/clickhouse-jdbc-bridge/security/advisories/GHSA-3w6p-8f82-gw8r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4104'} | null |
GHSA | GHSA-vp8g-53fw-r9f2 | Malicious Package in dynamo-schema | Version 0.0.3 of `dynamo-schema` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`
## Recommendation
If version 0.0.3 of this module is found installed you will want to replace it with a version before or after 0.0.3. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised. | null | 2021-09-24T17:28:16Z | 2020-09-01T19:54:44Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://github.com/advisories/GHSA-vp8g-53fw-r9f2', 'https://github.com/andrewjstone/dynamo-schema', 'https://snyk.io/vuln/SNYK-JS-DYNAMOSCHEMA-450992', 'https://www.npmjs.com/advisories/626'} | null |
GHSA | GHSA-8vq6-5f66-hp3r | Logic error in dolibarr/dolibarr | In dolibarr/dolibarr prior to 16.0 any low privileged users could update their login name which should only be updated by admin. | {'CVE-2022-0746'} | 2022-03-07T13:41:24Z | 2022-02-26T00:00:44Z | MODERATE | 4.3 | null | {'https://huntr.dev/bounties/b812ea22-0c02-46fe-b89f-04519dfb1ebd', 'https://github.com/advisories/GHSA-8vq6-5f66-hp3r', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0746', 'https://github.com/dolibarr/dolibarr/commit/4973019630d51ad76b7c1a4141ec7a33053a7d21'} | null |
GHSA | GHSA-xp4x-j9vh-c3wf | OS Command Injection and Command Injection in kill-port-process | The kill-port-process package version < 2.2.0 is vulnerable to a Command Injection vulnerability. | {'CVE-2019-15609'} | 2022-02-10T20:20:31Z | 2022-02-10T20:20:31Z | HIGH | 9.8 | {'CWE-77', 'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-15609', 'https://github.com/advisories/GHSA-xp4x-j9vh-c3wf', 'https://hackerone.com/reports/661959'} | null |
GHSA | GHSA-w96g-3p64-63wr | Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV | OpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has a buffer overflow in the cv::BmpDecoder::readData function in modules/imgcodecs/src/grfmt_bmp.cpp when reading an image file by using cv::imread, as demonstrated by the 4-buf-overflow-readData-memcpy test case. | {'CVE-2017-12601'} | 2021-12-01T15:05:53Z | 2021-10-12T22:01:23Z | HIGH | 8.8 | {'CWE-119', 'CWE-120'} | {'https://github.com/opencv/opencv-python/releases/tag/9', 'https://github.com/advisories/GHSA-w96g-3p64-63wr', 'https://github.com/opencv/opencv-python/releases/tag/11', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/pull/9376', 'https://security.gentoo.org/glsa/201712-02', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12601', 'https://github.com/opencv/opencv/issues/9309', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html', 'https://github.com/xiaoqx/pocs/blob/master/opencv.md'} | null |
GHSA | GHSA-xg2h-wx96-xgxr | RandomAlphaNumeric and CryptoRandomAlphaNumeric are not as random as they should be | ### Impact
A security-sensitive bug was discovered by Open Source Developer *Erik Sundell of Sundell Open Source Consulting AB*.
The functions `RandomAlphaNumeric(int)` and `CryptoRandomAlphaNumeric(int)` are not as random as they should be. Small values of `int` in the functions above will return a smaller subset of results than they should. For example, `RandomAlphaNumeric(1)` will always return a digit in the 0-9 range, while `RandomAlphaNumeric(4)` will return around ~7 million of the ~13M possible permutations.
This is considered a security release because programs that rely upon random generators for passwords are at an increased risk of brute force-style password guessing. There is also a higher probability of collision.
The problem was the result of a mistaken regular expression that only accepted random strings if they contained a digit from `[0-9]`. That restriction has been removed.
### Patches
This issue has been corrected in v1.0.2.
### Workarounds
If you cannot upgrade to v1.0.2, you can work around the issue by calling `RandomAlphaNumericCustom(N, true, true)`|`CryptoRandomAlphaNumericCustom(N, true, true)` instead. (Where `N` is the desired length, and `true` is the literal boolean `true`.) | null | 2021-05-21T16:26:06Z | 2021-05-21T16:26:06Z | LOW | 0 | null | {'https://github.com/advisories/GHSA-xg2h-wx96-xgxr', 'https://github.com/Masterminds/goutils/security/advisories/GHSA-xg2h-wx96-xgxr'} | null |
GHSA | GHSA-wc4g-r73w-x8mm | Insecure temporary file in Tensorflow | ### Impact
In multiple places, TensorFlow uses `tempfile.mktemp` to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in `mktemp` and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness).
In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the `mktemp` function usage.
### Patches
We have patched the issue in several commits, replacing `mktemp` with the safer `mkstemp`/`mkdtemp` functions, according to the usage pattern.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported on huntr.dev for one scenario and discovered via variant analysis on other instances. | {'CVE-2022-23563'} | 2022-02-11T15:07:15Z | 2022-02-09T23:54:51Z | HIGH | 7.1 | {'CWE-668', 'CWE-367'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23563', 'https://github.com/advisories/GHSA-wc4g-r73w-x8mm'} | null |
GHSA | GHSA-9gj3-hwp5-pmwc | XSS in the `altField` option of the Datepicker widget in jquery-ui | ### Impact
Accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:
```js
$( "#datepicker" ).datepicker( {
altField: "<img onerror='doEvilThing()' src='/404' />",
} );
```
will call the `doEvilThing` function.
### Patches
The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector.
### Workarounds
A workaround is to not accept the value of the `altField` option from untrusted sources.
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery UI repo](https://github.com/jquery/jquery-ui/issues). If you don't find an answer, open a new issue. | {'CVE-2021-41182'} | 2022-04-22T15:40:54Z | 2021-10-26T14:55:02Z | MODERATE | 6.5 | {'CWE-79'} | {'https://security.netapp.com/advisory/ntap-20211118-0004/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-9gj3-hwp5-pmwc', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NXIUUBRVLA4E7G7MMIKCEN75YN7UFERW/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SNXA7XRKGINWSUIPIZ6ZBCTV6N3KSHES/', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41182', 'https://github.com/jquery/jquery-ui/security/advisories/GHSA-9gj3-hwp5-pmwc', 'https://www.tenable.com/security/tns-2022-09', 'https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/', 'https://www.drupal.org/sa-contrib-2022-004', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O74SXYY7RGXREQDQUDQD4BPJ4QQTD2XQ/', 'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63', 'https://www.drupal.org/sa-core-2022-002'} | null |
GHSA | GHSA-36xw-fx78-c5r4 | containerd-shim API Exposed to Host Network Containers | ## Impact
Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges.
## Patches
This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade.
## Workarounds
If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with `docker run --net=host` or `hostNetwork: true` in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue.
If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to `deny unix addr=@**,` to your policy.
It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
## Credits
The containerd maintainers would like to thank Jeff Dileo of NCC Group for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md) and for reviewing the patch.
## For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug. | {'CVE-2020-15257'} | 2022-04-19T19:02:38Z | 2021-05-24T17:00:22Z | MODERATE | 5.2 | {'CWE-669'} | {'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad', 'https://github.com/advisories/GHSA-36xw-fx78-c5r4', 'https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4', 'https://github.com/containerd/containerd/releases/tag/v1.4.3', 'https://www.debian.org/security/2021/dsa-4865', 'https://security.gentoo.org/glsa/202105-33', 'https://research.nccgroup.com/2020/12/10/abstract-shimmer-cve-2020-15257-host-networking-is-root-equivalent-again/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15257'} | null |
GHSA | GHSA-r2qc-w64x-6j54 | XSS in Vega | Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. Vega in an npm package.
In Vega before version 5.17.3 there is an XSS vulnerability in Vega expressions. Through a specially crafted Vega expression, an attacker could
execute arbitrary javascript on a victim's machine.
This is fixed in version 5.17.3 | {'CVE-2020-26296'} | 2021-01-07T22:32:51Z | 2020-12-30T23:09:21Z | LOW | 8.7 | {'CWE-79'} | {'https://github.com/vega/vega/releases/tag/v5.17.3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26296', 'https://github.com/vega/vega/security/advisories/GHSA-r2qc-w64x-6j54', 'https://github.com/vega/vega/pull/3019', 'https://www.npmjs.com/package/vega', 'https://github.com/advisories/GHSA-r2qc-w64x-6j54', 'https://github.com/vega/vega/issues/3018'} | null |
GHSA | GHSA-wwgf-3xp7-cxj4 | Potentially sensitive data exposure in Symfony Web Socket Bundle | ### Impact
Inside `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()`, messages are arbitrarily broadcasted to the related Topic if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` does not succeed. The `dispatch()` method can be considered to not succeed if (depending on the version of the bundle) the callback defined on a topic route is misconfigured, a `Gos\Bundle\WebSocketBundle\Topic\TopicInterface` implementation is not found for the callback, a topic which also implements `Gos\Bundle\WebSocketBundle\Topic\SecuredTopicInterface` rejects the connection, or an Exception is unhandled. This can result in an unintended broadcast to the websocket server potentially with data that should be considered sensitive.
### Patches
In 1.10.4, 2.6.1, and 3.3.0, `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()` has been changed to no longer broadcast an event's data if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` fails.
### Workarounds
Upgrade to 1.10.4, 2.6.1, and 3.3.0
Note, the 1.x branch is considered end of support as of July 1, 2020.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle) | null | 2022-04-19T19:02:30Z | 2020-07-07T16:33:45Z | MODERATE | 5.9 | {'CWE-200'} | {'https://github.com/GeniusesOfSymfony/WebSocketBundle/security/advisories/GHSA-wwgf-3xp7-cxj4', 'https://github.com/FriendsOfPHP/security-advisories/commit/942fd37245cb724ba8cc8d6f11f075a1bd53b338', 'https://snyk.io/vuln/SNYK-PHP-GOSWEBSOCKETBUNDLE-575401', 'https://github.com/advisories/GHSA-wwgf-3xp7-cxj4'} | null |
GHSA | GHSA-9qj9-36jm-prpv | Regular Expression Denial of Service in fresh | Affected versions of `fresh` are vulnerable to regular expression denial of service when parsing specially crafted user input.
## Recommendation
Update to version 0.5.2 or later. | {'CVE-2017-16119'} | 2021-01-08T19:02:55Z | 2018-07-24T20:16:57Z | HIGH | 0 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-16119', 'https://www.npmjs.com/advisories/526', 'https://github.com/advisories/GHSA-9qj9-36jm-prpv', 'https://nodesecurity.io/advisories/526'} | null |
GHSA | GHSA-cc2p-4jhr-xhhx | False-positive validity for NFT1 genesis transactions in SLPJS | ### Impact
In the npm package named "slpjs", versions prior to 0.27.4 are vulnerable to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
### Patches
npm package "slpjs" has been patched and is published and tagged as version 0.27.4.
### Workarounds
Upgrade to slpjs 0.27.4.
### References
* Package location: https://www.npmjs.com/package/slpjs
* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements
* Git commit hash fixing this issue: https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c
* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7
### For more information
If you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slpjs/issues) repository. | {'CVE-2020-15130'} | 2021-01-07T23:43:06Z | 2020-07-30T14:58:42Z | CRITICAL | 7.5 | {'CWE-697'} | {'https://github.com/advisories/GHSA-cc2p-4jhr-xhhx', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15130', 'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c', 'https://github.com/simpleledger/slpjs/security/advisories/GHSA-cc2p-4jhr-xhhx'} | null |
GHSA | GHSA-24ww-mc5x-xc43 | Man-in-the-middle attack in Apache Cassandra | In Apache Cassandra, all versions prior to 2.1.22, 2.2.18, 3.0.22, 3.11.8 and 4.0-beta2, it is possible for a local attacker without access to the Apache Cassandra process or configuration files to manipulate the RMI registry to perform a man-in-the-middle attack and capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and perform unauthorised operations. Users should also be aware of CVE-2019-2684, a JRE vulnerability that enables this issue to be exploited remotely. | {'CVE-2020-13946'} | 2021-05-25T21:51:12Z | 2021-05-07T15:54:46Z | MODERATE | 5.9 | {'CWE-668'} | {'https://github.com/advisories/GHSA-24ww-mc5x-xc43', 'https://security.netapp.com/advisory/ntap-20210521-0005/', 'https://lists.apache.org/thread.html/rab8d90d28f944d84e4d7852f355a25c89451ae02c2decc4d355a9cfc@%3Cuser.cassandra.apache.org%3E', 'https://lists.apache.org/thread.html/r1fd117082b992e7d43c1286e966c285f98aa362e685695d999ff42f7@%3Cuser.cassandra.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13946', 'https://lists.apache.org/thread.html/rcd7544b24d8fc32b7950ec4c117052410b661babaa857fb1fc641152%40%3Cuser.cassandra.apache.org%3E', 'https://lists.apache.org/thread.html/r718e01f61b35409a4f7a3ccbc1cb5136a1558a9f9c2cb8d4ca9be1ce@%3Cuser.cassandra.apache.org%3E'} | null |
GHSA | GHSA-767j-jfh2-jvrc | Potential HTTP request smuggling in Apache Tomcat | The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely. | {'CVE-2019-17569'} | 2021-08-19T19:31:11Z | 2020-02-28T01:10:58Z | MODERATE | 4.8 | {'CWE-444'} | {'https://lists.apache.org/thread.html/rc31cbabb46cdc58bbdd8519a8f64b6236b2635a3922bbeba0f0e3743@%3Ccommits.tomee.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.debian.org/security/2020/dsa-4680', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://security.netapp.com/advisory/ntap-20200327-0005/', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://lists.apache.org/thread.html/r88def002c5c78534674ca67472e035099fbe088813d50062094a1390%40%3Cannounce.tomcat.apache.org%3E', 'https://github.com/advisories/GHSA-767j-jfh2-jvrc', 'https://lists.apache.org/thread.html/r7bc994c965a34876bd94d5ff15b4e1e30b6220a15eb9b47c81915b78@%3Ccommits.tomee.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17569', 'https://www.debian.org/security/2020/dsa-4673', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00025.html', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00006.html'} | null |
GHSA | GHSA-v9j2-q4q5-cxh4 | No CSRF protection on the password change form | ### Impact
It's possible for forge an URL that, when accessed by an admin, will reset the password of any user in XWiki.
### Patches
The problem has been patched in XWiki 12.10.5, 13.2RC1.
### Workarounds
It's possible to apply the patch manually by modifying the `register_macros.vm` template like in https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257.
### References
https://jira.xwiki.org/browse/XWIKI-18315
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki](https://jira.xwiki.org)
* Email us at [security ML](mailto:security@xwiki.org)
| {'CVE-2021-32730'} | 2021-07-02T19:19:13Z | 2021-07-02T19:19:13Z | MODERATE | 5.7 | {'CWE-352'} | {'https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-v9j2-q4q5-cxh4', 'https://jira.xwiki.org/browse/XWIKI-18315', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32730', 'https://github.com/advisories/GHSA-v9j2-q4q5-cxh4'} | null |
GHSA | GHSA-68wm-pfjf-wqp6 | Authentication bypassed with malformed request URI on nginx | ### Impact
This affects uses who are using nginx ngx_http_auth_request_module with Authelia, it allows a malicious individual who crafts a malformed HTTP request to bypass the authentication mechanism. It additionally could theoretically affect other proxy servers, but all of the ones we officially support except nginx do not allow malformed URI paths.
### Patches
The problem is rectified entirely in v4.29.3. As this patch is relatively straightforward we can back port this to any version upon request. Alternatively we are supplying a git patch to 4.25.1 which should be relatively straightforward to apply to any version, the git patches for specific versions can be found below.
<details><summary>Patch for 4.25.1:</summary><p>
```patch
From ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001
From: James Elliott <james-d-elliott@users.noreply.github.com>
Date: Wed, 19 May 2021 12:10:13 +1000
Subject: [PATCH] fix(handlers): verify returns 200 on malformed request
This is a git patch for commit at tag v4.25.1 to address a potential method to bypass authentication in proxies that forward malformed information to Authelia in the forward auth process. Instead of returning a 200 this ensures that Authelia returns a 401 when this occurs.
---
internal/handlers/handler_verify.go | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go
index 65c064ce..4dd9702d 100644
--- a/internal/handlers/handler_verify.go
+++ b/internal/handlers/handler_verify.go
@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques
targetURL, err := getOriginalURL(ctx)
if err != nil {
- ctx.Error(fmt.Errorf("Unable to parse target URL: %s", err), operationFailedMessage)
+ ctx.Logger.Error(fmt.Errorf("Unable to parse target URL: %s", err))
+ ctx.ReplyUnauthorized()
+
return
}
--
2.31.1
```
</p></details>
### Workarounds
The most relevant workaround is upgrading. **If you need assistance with an upgrade please contact us on [Matrix](https://riot.im/app/#/room/#authelia:matrix.org) or [Discord](https://discord.authelia.com).** Please just let us know you're needing help upgrading to above 4.29.2.
You can add an block which fails requests that contains a malformed URI in the internal location block. We have crafted one that should work in most instances, it basically checks no chars that are required to be URL-encoded for either the path or the query are in the URI. Basically this regex checks that the characters between the square braces are the only characters in the $request_uri header, if they exist, it returns a HTTP 401 status code. The characters in the regex match are tested to not cause a parsing error that would result in a failure, however they are not exhaustive since query strings seem to not always conform to the RFC.
<details><summary>authelia.conf:</summary><p>
```nginx
location /authelia {
internal;
# **IMPORTANT**
# This block rejects requests with a 401 which contain characters that are unable to be parsed.
# It is necessary for security prior to v4.29.3 due to the fact we returned an invalid code in the event of a parser error.
# You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.
# RFC3986: http://tools.ietf.org/html/rfc3986
# Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/
if ($request_uri ~ [^a-zA-Z0-9_+-=\!@$%&*?~.:#'\;\(\)\[\]]) {
return 401;
}
# Include the remainder of the block here.
}
````
</p></details>
### Discovery
This issue was discovered by:
Siemens Energy
Cybersecurity Red Team
- Silas Francisco
- Ricardo Pesqueira
### Identifying active exploitation of the vulnerability
The following regex should match log entries that are an indication of the vulnerability being exploited:
```regex
level=error msg="Unable to parse target URL: Unable to parse URL (extracted from X-Original-URL header)?.*?: parse.*?net/url:.*github\.com/authelia/authelia/internal/handlers/handler_verify\.go
```
Example log entry ***with*** X-Original-URL configured:
```log
time="2021-05-21T16:31:15+10:00" level=error msg="Unable to parse target URL: Unable to parse URL extracted from X-Original-URL header: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
Example log entry ***without*** X-Original-URL configured:
```log
time="2021-05-21T16:30:17+10:00" level=error msg="Unable to parse target URL: Unable to parse URL https://example.com/: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [authelia](https://github.com/authelia/authelia/issues)
* Email us at [security@authelia.com](mailto:security@authelia.com)
| {'CVE-2021-32637'} | 2022-04-19T19:02:58Z | 2021-12-20T16:57:16Z | CRITICAL | 10 | {'CWE-287'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda', 'https://github.com/advisories/GHSA-68wm-pfjf-wqp6', 'https://github.com/authelia/authelia/security/advisories/GHSA-68wm-pfjf-wqp6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32637'} | null |
GHSA | GHSA-mr6r-mvw4-736g | Vyper interfaces returning integer types less than 256 bits can be manipulated if uint256 is used | # VVE-2020-0001
Earlier today, we received a responsible disclosure of a potential issue from @montyly (security researcher at @trailofbits) for Vyper users who make assumptions about what values certain interface types can return.
### Impact
We determined the issue to be mild and unlikely to be exploited, with an easy workaround while the correct resolution is in process. The issue stems from a number of things, which we will detail here.
(1) The ABI Specification is under-defined such that function return type is not always reflected in how you use it
This means that a function which returns `uint8` under the hood actually returns a 32 byte integer, making it identical to a function that returns `uint256`. This allows users to read an interface that returns a `uint8` value to be stored into a `uint256` variable without any explicit casting or input validation.
(2) Vyper doesn't have `uint8` types
When Vyper was originally created, it only had one numeric type, but we added just enough types to be able to work with the majority of ERC interfaces that exist.
Unfortunately, we never added `uint8`, because it's only majority usage was for `ERC20.decimals()` as the return type, which isn't reflected in the method ID. Because of (1), it didn't matter that we didn't have these types implemented because you could capture the return value as `uint256` and use it just fine.
(3) `ERC20.decimals()` returns `uint8`
`ERC20.decimal()` (which is an optional function) returns a `uint8` type. While it was never intentioned to be used directly within a smart contract (hence being optional), someone could easily make the decision to rely on it to perform important functionality within their Vyper smart contract. This might lead to a scenario where an unexpectedly large value (> 255) returned by calling this function (which a malicious contract writer might write) would allow an attacker to manipulate or bypass certain logic depending on this value.
In summary, because of (1), it isn't necessary to have to cast the return value of a function that returns `uint8` to `uint256`, and because of (2) it isn't possible to have the type system protect against this type of error. This could lead to scenarios like (3) where this behavior can be exploited.
### Patches
We are currently refactoring our typing system so we can implement all ABI-compliant integer types, but no currently patched version is available that gives users access to the `uint8` type.
### Workarounds
There is an easy workaround where you should check that the value returned by an interface which specifies `uint8` should be checked to be within the bounds of a `uint8` integer. As an example:
```python
...
# returns uint8, but we implicitly cast to uint256 without checking
decimals: uint256 = ERC20(_token).decimal()
# FIX: Insert this line
assert decimals < 256
...
```
Depending on how you use this value, it may not be necessary to insert this check.
### References
* [ABI Specification](https://solidity.readthedocs.io/en/latest/abi-spec.html)
### For more information
If you have any questions or comments about this advisory:
* Chat with us in [our gitter ](https://gitter.im/vyperlang/community)
* Open an issue in [https://github.com/vyperlang/vyper](https://github.com/vyperlang/vyper)
* Email us at [security@vyperlang.org](mailto:security@vyperlang.org) | null | 2022-04-19T19:02:24Z | 2020-03-25T18:20:19Z | LOW | 0 | null | {'https://github.com/vyperlang/vyper/security/advisories/GHSA-mr6r-mvw4-736g', 'https://github.com/advisories/GHSA-mr6r-mvw4-736g'} | null |
GHSA | GHSA-2rqw-v265-jf8c | Open Redirect in ActionPack | # Overview
There is a possible open redirect vulnerability in the Host Authorization
middleware in Action Pack. This vulnerability has been assigned the CVE
identifier CVE-2021-22942.
Versions Affected: >= 6.0.0.
Not affected: < 6.0.0
Fixed Versions: 6.1.4.1, 6.0.4.1
# Impact
Specially crafted “X-Forwarded-Host” headers in combination with certain
“allowed host” formats can cause the Host Authorization middleware in
Action Pack to redirect users to a malicious website.
Impacted applications will have allowed hosts with a leading dot.
For example, configuration files that look like this:
```ruby
config.hosts << '.EXAMPLE.com'
```
When an allowed host contains a leading dot, a specially crafted
Host header can be used to redirect to a malicious website.
This vulnerability is similar to CVE-2021-22881, but CVE-2021-22881 did not
take in to account domain name case sensitivity.
# Releases
The fixed releases are available at the normal locations.
# Workarounds
In the case a patch can’t be applied, the following monkey patch can be
used in an initializer:
```ruby
module ActionDispatch
class HostAuthorization
HOSTNAME = /[a-z0-9.-]+|\[[a-f0-9]*:[a-f0-9.:]+\]/i
VALID_ORIGIN_HOST = /\A(#{HOSTNAME})(?::\d+)?\z/
VALID_FORWARDED_HOST = /(?:\A|,[ ]?)(#{HOSTNAME})(?::\d+)?\z/
private
def authorized?(request)
origin_host =
request.get_header("HTTP_HOST")&.slice(VALID_ORIGIN_HOST, 1) || ""
forwarded_host =
request.x_forwarded_host&.slice(VALID_FORWARDED_HOST, 1) || ""
@permissions.allows?(origin_host) &&
(forwarded_host.blank? || @permissions.allows?(forwarded_host))
end
end
end
```
| {'CVE-2021-22942'} | 2021-12-15T00:05:07Z | 2021-08-26T20:36:51Z | HIGH | 0 | {'CWE-601'} | {'https://groups.google.com/g/rubyonrails-security/c/wB5tRn7h36c', 'http://www.openwall.com/lists/oss-security/2021/12/14/5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22942', 'https://access.redhat.com/security/cve/cve-2021-22942', 'https://weblog.rubyonrails.org/2021/8/19/Rails-6-0-4-1-and-6-1-4-1-have-been-released/', 'https://github.com/advisories/GHSA-2rqw-v265-jf8c', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2021-22942.yml', 'https://rubygems.org/gems/actionpack'} | null |
GHSA | GHSA-7r2x-3qcm-8vfw | Downloads Resources over HTTP in herbivore | Affected versions of `herbivore` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `herbivore`.
## Recommendation
The module author has rewritten much of the package, and in that process, patched the vulnerability, but has not published any of the new code to npm.
In order to get an updated version, it is necessary to install the package from github. This can be done using the following command:
```
npm i samatt/herbivore
``` | {'CVE-2016-10665'} | 2021-01-08T19:14:21Z | 2019-02-18T23:44:36Z | HIGH | 0 | {'CWE-311'} | {'https://github.com/samatt/herbivore', 'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3', 'https://nodesecurity.io/advisories/258', 'https://www.npmjs.com/advisories/258', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10665', 'https://github.com/advisories/GHSA-7r2x-3qcm-8vfw'} | null |
GHSA | GHSA-cph5-m8f7-6c5x | Incorrect Comparison in axios | axios is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3749'} | 2022-05-05T13:51:38Z | 2021-09-01T18:23:02Z | HIGH | 7.5 | {'CWE-400', 'CWE-697'} | {'https://lists.apache.org/thread.html/rfa094029c959da0f7c8cd7dc9c4e59d21b03457bf0cedf6c93e1bb0a@%3Cdev.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r7324ecc35b8027a51cb6ed629490fcd3b2d7cf01c424746ed5744bf1@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/ra15d63c54dc6474b29f72ae4324bcb03038758545b3ab800845de7a1@%3Ccommits.druid.apache.org%3E', 'https://github.com/advisories/GHSA-cph5-m8f7-6c5x', 'https://lists.apache.org/thread.html/rc263bfc5b53afcb7e849605478d73f5556eb0c00d1f912084e407289@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r075d464dce95cd13c03ff9384658edcccd5ab2983b82bfc72b62bb10@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r216f0fd0a3833856d6a6a1fada488cadba45f447d87010024328ccf2@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfc5c478053ff808671aef170f3d9fc9d05cc1fab8fb64431edc66103@%3Ccommits.druid.apache.org%3E', 'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929', 'https://lists.apache.org/thread.html/r4bf1b32983f50be00f9752214c1b53738b621be1c2b0dbd68c7f2391@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r74d0b359408fff31f87445261f0ee13bdfcac7d66f6b8e846face321@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r3ae6d2654f92c5851bdb73b35e96b0e4e3da39f28ac7a1b15ae3aab8@%3Ccommits.druid.apache.org%3E', 'https://www.npmjs.com/package/axios', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3749', 'https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31'} | null |
GHSA | GHSA-3756-hwhv-qw58 | Cross site scripting in francoisjacquet/rosariosis | A Cross Site Scripting vulnerability exists RosarioSIS before 4.3 via the SanitizeMarkDown function in ProgramFunctions/MarkDownHTML.fnc.php. | {'CVE-2021-44566'} | 2022-03-04T21:38:44Z | 2022-02-25T00:01:08Z | MODERATE | 5.4 | {'CWE-79'} | {'https://gitlab.com/francoisjacquet/rosariosis/-/commit/81886abb45a32e802151660de674f084afaef3aa', 'https://gitlab.com/francoisjacquet/rosariosis/-/issues/259', 'https://gitlab.com/francoisjacquet/rosariosis/-/blob/mobile/CHANGES_V3_4.md#changes-in-43', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44566', 'https://github.com/advisories/GHSA-3756-hwhv-qw58'} | null |
GHSA | GHSA-q9wr-gcjc-hq52 | Prototype Pollution in reggae | All versions of `reggae` are vulnerable to prototype pollution. The function `set` does not restrict the modification of an Object's prototype, which may allow a malicious to add or modify an existing property that will exist on all objects.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2021-10-01T20:09:48Z | 2020-09-04T15:12:13Z | HIGH | 0 | {'CWE-1321'} | {'https://www.npmjs.com/advisories/1331', 'https://github.com/advisories/GHSA-q9wr-gcjc-hq52'} | null |
GHSA | GHSA-6jv7-28mv-qp9c | Missing permission check in Jenkins autonomiq Plugin | A missing permission check in Jenkins autonomiq Plugin 1.15 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials. | {'CVE-2022-25195'} | 2022-05-04T20:59:05Z | 2022-02-16T00:01:23Z | MODERATE | 4.3 | {'CWE-862'} | {'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25195', 'https://github.com/advisories/GHSA-6jv7-28mv-qp9c', 'https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2545'} | null |
GHSA | GHSA-c3gv-9cxf-6f57 | Cross-site Scripting in Loofah | In the Loofah gem for Ruby through v2.3.0 unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished. | {'CVE-2019-15587'} | 2021-01-08T20:40:07Z | 2019-11-05T23:58:25Z | LOW | 0 | {'CWE-79'} | {'https://hackerone.com/reports/709009', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15587', 'https://usn.ubuntu.com/4498-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4WK2UG7ORKRQOJ6E4XJ2NVIHYJES6BYZ/', 'https://www.debian.org/security/2019/dsa-4554', 'https://github.com/advisories/GHSA-c3gv-9cxf-6f57', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XMCWPLYPNIWYAY443IZZJ4IHBBLIHBP5/', 'https://security.netapp.com/advisory/ntap-20191122-0003/', 'https://github.com/flavorjones/loofah/issues/171'} | null |
GHSA | GHSA-fr28-569j-53c4 | Incorrect Default Permissions | An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077. | {'CVE-2020-24584'} | 2021-03-18T20:30:01Z | 2021-03-18T20:30:01Z | HIGH | 7.5 | {'CWE-276'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F2ZHO3GZCJMP3DDTXCNVFV6ED3W64NAU/', 'https://security.netapp.com/advisory/ntap-20200918-0004/', 'https://github.com/django/django/commit/1853724acaf17ed7414d54c7d2b5563a25025a71', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24584', 'https://www.openwall.com/lists/oss-security/2020/09/01/2', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://github.com/advisories/GHSA-fr28-569j-53c4', 'https://usn.ubuntu.com/4479-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZCRPQCBTV3RZHKVZ6K6QOAANPRZQD3GI/', 'https://www.djangoproject.com/weblog/2020/sep/01/security-releases/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OLGFFLMF3X6USMJD7V5F5P4K2WVUTO3T/', 'https://groups.google.com/forum/#!topic/django-announce/Gdqn58RqIDM', 'https://groups.google.com/forum/#!topic/django-announce/zFCMdgUnutU'} | null |
GHSA | GHSA-2pwh-52h7-7j84 | JavaScript execution via malicious molfiles (XSS) | ### Impact
The viewer plugin implementation of `<mol:molecule>` renders molfile data directly inside a `<script>` tag without any escaping. Arbitrary JavaScript code can thus be executed in the client browser via crafted molfiles.
### Patches
Patched in v0.3.0: Molfile data is now rendered as value of a hidden `<input>` tag and escaped via JSF's mechanisms.
### Workarounds
No workaround available. | null | 2021-04-16T19:52:49Z | 2021-04-16T19:52:49Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/ipb-halle/MolecularFaces/security/advisories/GHSA-2pwh-52h7-7j84', 'https://github.com/advisories/GHSA-2pwh-52h7-7j84'} | null |
GHSA | GHSA-fx7m-j728-mjw3 | Moderate severity vulnerability that affects uap-core | An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser UAP-Core before 0.6.0. A Regular Expression Denial of Service (ReDoS) issue allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to a value containing a long digit string. (The UAP-Core project contains the vulnerability, propagating to all implementations.) | {'CVE-2018-20164'} | 2021-09-10T20:12:02Z | 2019-03-06T17:35:47Z | MODERATE | 5.3 | {'CWE-185'} | {'https://www.x41-dsec.de/lab/advisories/x41-2018-009-uaparser/', 'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc', 'https://github.com/advisories/GHSA-fx7m-j728-mjw3', 'https://github.com/ua-parser/uap-core/issues/332', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20164', 'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014'} | null |
GHSA | GHSA-jqjg-v355-hr9q | Malicious Package in buffer-xop | Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.
## Recommendation
Remove the package from your environment. Ensure no Ethereum funds were compromised. | null | 2021-09-29T21:12:22Z | 2020-09-03T22:11:02Z | CRITICAL | 9.8 | {'CWE-506'} | {'https://www.npmjs.com/advisories/1250', 'https://github.com/advisories/GHSA-jqjg-v355-hr9q'} | null |
GHSA | GHSA-cv3v-7846-6pxm | Unauthorized File Access in node-git-server | Versions of `node-git-server` prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories.
## Recommendation
Upgrade to version 0.6.1 or later. | null | 2021-09-29T19:59:02Z | 2020-09-03T21:15:19Z | HIGH | 7.5 | {'CWE-552'} | {'https://snyk.io/vuln/SNYK-JS-NODEGITSERVER-474343', 'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43', 'https://www.npmjs.com/advisories/1214', 'https://github.com/gabrielcsapo/node-git-server/pull/62', 'https://github.com/advisories/GHSA-cv3v-7846-6pxm'} | null |
GHSA | GHSA-q324-q795-2q5p | Path traversal when using `preview-docs` when working dir contains files with question mark `?` in name | ### Impact
`preview-docs` command allows path traversal if current working dir contains files with question mark `?` in name and attacker knows the name.
### Patches
It was patched starting from 1.0.0-beta.59
### Workarounds
Do not run openapi-cli preview-docs command in the folder which contains files with question mark `?` in name.
### References
https://github.com/Redocly/openapi-cli/pull/347
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [@redocly/openapi-cli](https://github.com/Redocly/openapi-cli)
* Email us at [security@redocly.com](mailto:security@redocly.com)
| null | 2022-04-19T19:03:11Z | 2021-10-12T16:05:11Z | LOW | 0 | null | {'https://github.com/advisories/GHSA-q324-q795-2q5p', 'https://github.com/Redocly/openapi-cli/pull/347', 'https://github.com/Redocly/openapi-cli/security/advisories/GHSA-q324-q795-2q5p'} | null |
GHSA | GHSA-j636-crp3-m584 | Cross-site Scripting in tableexport.jquery.plugin | There is a cross-site scripting vulnerability with default `onCellHtmlData` function in GitHub repository hhurz/tableexport.jquery.plugin prior to 1.25.0. This can result in transmitting cookies to third-party servers and/or sending data from secure sessions to third-party servers. | {'CVE-2022-1291'} | 2022-04-22T20:17:23Z | 2022-04-11T00:00:22Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1291', 'https://huntr.dev/bounties/49a14371-6058-47dd-9801-ec38a7459fc5', 'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9', 'https://github.com/advisories/GHSA-j636-crp3-m584'} | null |
GHSA | GHSA-m6wg-2mwg-4rfq | Use After Free | The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification. | {'CVE-2020-8945'} | 2021-05-18T15:29:42Z | 2021-05-18T15:29:42Z | HIGH | 7.5 | {'CWE-416'} | {'https://github.com/proglottis/gpgme/pull/23', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://access.redhat.com/errata/RHSA-2020:0679', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H6P6SSNKN4H6GSEVROHBDXA64PX7EOED/', 'https://access.redhat.com/errata/RHSA-2020:0697', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WXV7NZELYWRRCXATXU3FYD3G3WJT3WYM/', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://bugzilla.redhat.com/show_bug.cgi?id=1795838', 'https://github.com/advisories/GHSA-m6wg-2mwg-4rfq', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8945', 'https://access.redhat.com/errata/RHSA-2020:0689', 'https://github.com/proglottis/gpgme/compare/v0.1.0...v0.1.1', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KDBT77KV3U7BESJX3P4S4MPVDGRTAQA2/'} | null |
GHSA | GHSA-cgpw-2gph-2r9g | Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.App, and Microsoft.AspNetCore.Server.Kestrel.Core | Microsoft is aware of a denial of service vulnerability in ASP.NET Core when a malformed request is terminated. An attacker who successfully exploited this vulnerability could cause a denial of service attack.
The update addresses the vulnerability by correcting how ASP.NET Core handles such requests.
| null | 2021-12-03T14:28:11Z | 2018-10-16T19:59:59Z | MODERATE | 0 | null | {'https://github.com/aspnet/Announcements/issues/311', 'https://github.com/advisories/GHSA-cgpw-2gph-2r9g'} | null |
GHSA | GHSA-243q-g9j3-qf6r | non-admin users can create integration role with administrator role | ### Impact
non-admin users can create integration role with administrator role
### Patches
We recommend updating to the current version 6.4.1.1. You can get the update to 6.4.1.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
| null | 2021-06-28T18:21:01Z | 2021-06-28T18:21:01Z | MODERATE | 0 | null | {'https://github.com/shopware/platform/security/advisories/GHSA-243q-g9j3-qf6r', 'https://github.com/advisories/GHSA-243q-g9j3-qf6r'} | null |
GHSA | GHSA-j3wh-5m26-2pf7 | Downloads Resources over HTTP in mystem-fix | Affected versions of `mystem-fix` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `mystem-fix`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees. | {'CVE-2016-10698'} | 2021-01-08T18:37:00Z | 2018-07-27T14:34:11Z | HIGH | 0 | {'CWE-311'} | {'https://www.npmjs.com/advisories/301', 'https://nodesecurity.io/advisories/301', 'https://github.com/advisories/GHSA-j3wh-5m26-2pf7', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10698'} | null |
GHSA | GHSA-whw7-h25v-9qvx | Moderate severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9, and org.apache.cxf.fediz:fediz-spring2 | Apache CXF Fediz ships with a number of container-specific plugins to enable WS-Federation for applications. A CSRF (Cross Style Request Forgery) style vulnerability has been found in the Spring 2, Spring 3, Jetty 8 and Jetty 9 plugins in Apache CXF Fediz prior to 1.4.0, 1.3.2 and 1.2.4. | {'CVE-2017-7661'} | 2021-06-17T19:01:16Z | 2018-10-18T16:56:38Z | MODERATE | 0 | {'CWE-352'} | {'https://lists.apache.org/thread.html/rc774278135816e7afc943dc9fc78eb0764f2c84a2b96470a0187315c@%3Ccommits.cxf.apache.org%3E', 'http://www.securitytracker.com/id/1038497', 'https://lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4@%3Ccommits.cxf.apache.org%3E', 'https://github.com/advisories/GHSA-whw7-h25v-9qvx', 'http://cxf.apache.org/security-advisories.data/CVE-2017-7661.txt.asc', 'https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf@%3Ccommits.cxf.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2017-7661', 'https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4@%3Ccommits.cxf.apache.org%3E'} | null |
GHSA | GHSA-2xpp-75vr-22vq | Low severity vulnerability that affects org.apache.nifi:nifi | The X-Frame-Options headers were applied inconsistently on some HTTP responses, resulting in duplicate or missing security headers. Some browsers would interpret these results incorrectly, allowing clickjacking attacks. Mitigation: The fix to consistently apply the security headers was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release. | {'CVE-2018-17192'} | 2021-08-31T20:20:26Z | 2018-12-20T22:02:24Z | MODERATE | 6.5 | {'CWE-1021'} | {'https://github.com/advisories/GHSA-2xpp-75vr-22vq', 'https://nvd.nist.gov/vuln/detail/CVE-2018-17192', 'https://nifi.apache.org/security.html#CVE-2018-17192'} | null |
GHSA | GHSA-q39c-5vh5-vw2p | Improper Authentication in Apereo CAS | Apereo CAS 5.3.x before 5.3.16, 6.x before 6.1.7.2, 6.2.x before 6.2.4, and 6.3.x before 6.3.0-RC4 mishandles secret keys with Google Authenticator for multifactor authentication. | {'CVE-2020-27178'} | 2021-08-02T16:47:10Z | 2021-08-02T16:47:10Z | HIGH | 7.5 | {'CWE-287'} | {'https://apereo.github.io/2020/10/14/gauthvuln/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27178', 'https://github.com/advisories/GHSA-q39c-5vh5-vw2p'} | null |
GHSA | GHSA-9c4x-5hgq-q3wh | Instance config inline secret exposure in Grafana | ### Impact
Some inline secrets are exposed in plaintext over the Grafana Agent HTTP server:
* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config`
* Inline secrets for integrations are exposed at `/-/config`
* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.
* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.
* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.
Inline secrets will be exposed to anyone being able to reach these endpoints.
Secrets found in these sections are used for:
* Delivering metrics to a Prometheus Remote Write system
* Authenticating against a system for discovering Prometheus targets
* Authenticating against a system for collecting metrics (scrape_configs and integrations)
* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode
* Authenticating against Kafka for receiving traces
Non-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability.
### Patches
Download [v0.20.1](https://github.com/grafana/agent/releases/tag/v0.20.1) or any version past [v0.21.2](https://github.com/grafana/agent/releases/tag/v0.21.2) to patch Grafana Agent. These patches obfuscate the listed impacted secrets from the vulnerable endpoints.
The patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.
### Workarounds
If for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.
You also may desire to restrict API access to Grafana Agent, with some combination of:
* Restrict network interfaces Grafana Agent listens on through `http_listen_address` in the `server` block. `127.0.0.1` is the most restrictive, `0.0.0.0` is the default.
* Configure Grafana Agent to use HTTPS with client authentication.
* Use firewall rules to restrict external access to Grafana Agent's API. | {'CVE-2021-41090'} | 2022-04-01T20:13:45Z | 2021-12-08T19:52:40Z | MODERATE | 6.5 | {'CWE-200', 'CWE-312'} | {'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11', 'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/security/advisories/GHSA-9c4x-5hgq-q3wh', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41090', 'https://github.com/advisories/GHSA-9c4x-5hgq-q3wh', 'https://github.com/grafana/agent/pull/1152', 'https://github.com/grafana/agent/releases/tag/v0.21.2', 'https://security.netapp.com/advisory/ntap-20211229-0004/', 'https://github.com/grafana/agent/releases/tag/v0.20.1'} | null |
GHSA | GHSA-h4hr-7fg3-h35w | Denial of service in prismjs | The package prismjs before 1.23.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the prism-asciidoc, prism-rest, prism-tap and prism-eiffel components. | {'CVE-2021-23341'} | 2021-03-01T19:52:33Z | 2021-03-01T19:52:33Z | HIGH | 0 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JS-PRISMJS-1076581', 'https://github.com/PrismJS/prism/pull/2584', 'https://github.com/advisories/GHSA-h4hr-7fg3-h35w', 'https://www.npmjs.com/package/prismjs', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23341', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1076582', 'https://github.com/PrismJS/prism/issues/2583', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1076583', 'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.