Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qh32-6jjc-qprm - https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f04
ensorflow/security/advisories/GHSA-qh32-6jjc-qprm - https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8 - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
CVE ID: CVE-2020-15210 State: PUBLISHED Published: 2020-09-25T18:45:30 Last Updated: 2024-08-04T13:08:22.871Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H) Vendors: tensorflow Products: tensorflow Problem Types: CWE-20 Description: In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and 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, o
leases 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. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2 - https://github.com/tensorflow/tensorflow/commit/d58c96946b2880991d63d1dacacb32f0a4dfa453 - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
CVE ID: CVE-2020-15211 State: PUBLISHED Published: 2020-09-25T18:45:24 Last Updated: 2024-08-04T13:08:22.936Z Severity: MEDIUM (CVSS 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N) Vendors: tensorflow Products: tensorflow Problem Types: CWE-125, CWE-787 Description: In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing
ors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative `-1` value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the `-1` index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the
allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue is patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83), and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that only operators which accept optional inputs use the `-1` special value and only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgra
only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgrading to the patched code. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45 - https://github.com/tensorflow/tensorflow/commit/46d5b0852528ddfd614ded79bccc75589f801bd9 - https://github.com/tensorflow/tensorflow/commit/00302787b788c5ff04cb6f62aed5a74d936e86c0 - https://github.com/tensorflow/tensorflow/commit/e11f55585f614645b360563072ffeb5c3eeff162 - https://github.com/tensorflow/tensorflow/commit/cd31fd0ce0449a9e0f83dc
commit/e11f55585f614645b360563072ffeb5c3eeff162 - https://github.com/tensorflow/tensorflow/commit/cd31fd0ce0449a9e0f83dcad08d6ed7f1d6bef3f - https://github.com/tensorflow/tensorflow/commit/1970c2158b1ffa416d159d03c3370b9a462aee35 - https://github.com/tensorflow/tensorflow/commit/fff2c8326280c07733828f990548979bdc893859 - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
CVE ID: CVE-2020-15212 State: PUBLISHED Published: 2020-09-25T18:50:34 Last Updated: 2024-08-04T13:08:22.919Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H) Vendors: tensorflow Products: tensorflow Problem Types: CWE-787 Description: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other
ight result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inferenc
re generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hx2x-85gr-wrpq
CVE ID: CVE-2020-15213 State: PUBLISHED Published: 2020-09-25T18:50:29 Last Updated: 2024-08-04T13:08:22.853Z Severity: MEDIUM (CVSS 4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L) Vendors: tensorflow Products: tensorflow Problem Types: CWE-119, CWE-770 Description: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae17
a very large value to trigger a large allocation. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. Additional Analyst Notes: - CVE Progra
here are no possible workaround and users are advised to upgrade to patched code. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87
CVE ID: CVE-2020-15214 State: PUBLISHED Published: 2020-09-25T18:50:23 Last Updated: 2024-08-04T13:08:22.895Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H) Vendors: tensorflow Products: tensorflow Problem Types: CWE-787 Description: In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output ar
This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids a
he case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 - https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm - https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a
CVE ID: CVE-2020-15215 State: PUBLISHED Published: 2020-10-06T18:00:17 Last Updated: 2024-08-04T13:08:22.830Z Severity: MEDIUM (CVSS 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L) Vendors: electron Products: electron Problem Types: CWE-693, CWE-668 Description: Electron before versions 11.0.0-beta.6, 10.1.2, 9.3.1 or 8.5.2 is vulnerable to a context isolation bypass. Apps using both `contextIsolation` and `sandbox: true` are affected. Apps using both `contextIsolation` and `nodeIntegrationInSubFrames: true` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privilege
ode running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/electron/electron/security/advisories/GHSA-56pc-6jqp-xqj8
CVE ID: CVE-2020-15216 State: PUBLISHED Published: 2020-09-29T16:00:18 Last Updated: 2024-08-04T13:08:22.878Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N) Vendors: russellhaering Products: goxmldsig Problem Types: CWE-347 Description: In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 or version 1.1.0 Additional Analyst Notes: - CVE Program Container: References: - https://github
e26a0436212b19cb9615e64 or version 1.1.0 Additional Analyst Notes: - CVE Program Container: References: - https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7 - https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64 - https://pkg.go.dev/github.com/russellhaering/goxmldsig?tab=overview - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZECBFD4M4PHBMBOCMSQ537NOU37QOVWP/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GUH33FPUXED3FHYL25BJOQPRKFGPOMS2/
CVE ID: CVE-2020-15217 State: PUBLISHED Published: 2020-10-07T19:10:13 Last Updated: 2024-08-04T13:08:22.923Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: glpi-project Products: glpi Problem Types: CWE-79 Description: In GLPI before version 9.5.2, there is a leakage of user information through the public FAQ. The issue was introduced in version 9.5.0 and patched in 9.5.2. As a workaround, disable public access to the FAQ. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/security/advisories/GHSA-x9hg-j29f-wvvv - https://github.com/glpi-project/glpi/commit/39e25591efddc560e3679ab07e443ee6198705e2
CVE ID: CVE-2020-15218 State: PUBLISHED Published: 2021-01-13T16:50:12 Last Updated: 2024-08-04T13:08:22.897Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N) Vendors: Combodo Products: iTop Problem Types: CWE-613 Description: Combodo iTop is a web based IT Service Management tool. In iTop before versions 2.7.2 and 3.0.0, admin pages are cached, so that their content is visible after deconnection by using the browser back button. This is fixed in versions 2.7.2 and 3.0.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Combodo/iTop/security/advisories/GHSA-3m3g-86hp-5p2j
CVE ID: CVE-2020-15219 State: PUBLISHED Published: 2021-01-13T16:55:17 Last Updated: 2024-08-04T13:08:22.809Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Vendors: Combodo Products: iTop Problem Types: CWE-209 Description: Combodo iTop is a web based IT Service Management tool. In iTop before versions 2.7.2 and 3.0.0, when a download error is triggered in the user portal, an SQL query is displayed to the user. This is fixed in versions 2.7.2 and 3.0.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Combodo/iTop/security/advisories/GHSA-q5cf-46rg-frf8
CVE ID: CVE-2020-15220 State: PUBLISHED Published: 2021-01-13T17:05:17 Last Updated: 2024-08-04T13:08:22.815Z Severity: MEDIUM (CVSS 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) Vendors: Combodo Products: iTop Problem Types: CWE-613 Description: Combodo iTop is a web based IT Service Management tool. In iTop before versions 2.7.2 and 3.0.0, two cookies are created for the same session, which leads to a possibility to steal user session. This is fixed in versions 2.7.2 and 3.0.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Combodo/iTop/security/advisories/GHSA-qw4q-cmcv-7vv2
CVE ID: CVE-2020-15221 State: PUBLISHED Published: 2021-01-13T17:10:15 Last Updated: 2024-08-04T13:08:23.137Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N) Vendors: Combodo Products: iTop Problem Types: CWE-79 Description: Combodo iTop is a web based IT Service Management tool. In iTop before versions 2.7.2 and 3.0.0, by modifying target browser local storage, an XSS can be generated in the iTop console breadcrumb. This is fixed in versions 2.7.2 and 3.0.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Combodo/iTop/security/advisories/GHSA-w6g2-p7pf-7hvw
CVE ID: CVE-2020-15222 State: PUBLISHED Published: 2020-09-24T16:15:52 Last Updated: 2024-08-04T13:08:22.899Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) Vendors: ory Products: fosite Problem Types: CWE-287 Description: In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the `jti` value is not checked. When using client authentication method "private_key_jwt", OpenId specification says the following about assertion `jti`: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless condition
er for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43 - https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9 - https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
CVE ID: CVE-2020-15223 State: PUBLISHED Published: 2020-09-24T16:15:45 Last Updated: 2024-08-04T13:08:22.904Z Severity: HIGH (CVSS 8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N) Vendors: ory Products: fosite Problem Types: CWE-755 Description: In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.34.0, the `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store. This is fixed in version 0.34.0 Additional Analyst Notes: - CVE Program
s on the ability to trigger errors in the store. This is fixed in version 0.34.0 Additional Analyst Notes: - CVE Program Container: References: - https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm - https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319 - https://tools.ietf.org/html/rfc7009#section-2.2.1
CVE ID: CVE-2020-15224 State: PUBLISHED Published: 2020-10-14T18:35:17 Last Updated: 2024-08-04T13:08:22.881Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) Vendors: openenclave Products: openenclave Problem Types: CWE-552 Description: In Open Enclave before version 0.12.0, an information disclosure vulnerability exists when an enclave application using the syscalls provided by the sockets.edl is loaded by a malicious host application. An attacker who successfully exploited the vulnerability could read privileged data from the enclave heap across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a special
rust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information otherwise considered confidential in an enclave, which could be used in further compromises. The issue has been addressed in version 0.12.0 and the current master branch. Users will need to to recompile their applications against the patched libraries to be protected from this vulnerability. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/openenclave/openenclave/security/advisories/GHSA-525h-wxc
tes: - CVE Program Container: References: - https://github.com/openenclave/openenclave/security/advisories/GHSA-525h-wxcc-f66m - https://github.com/openenclave/openenclave/blob/master/CHANGELOG.md#v0120 - https://github.com/openenclave/openenclave/commit/bcac8e7acb514429fee9e0b5d0c7a0308fd4d76b
CVE ID: CVE-2020-15225 State: PUBLISHED Published: 2021-04-29T00:00:00 Last Updated: 2024-08-04T13:08:22.886Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: carltongibson Products: django-filter Problem Types: CWE-681 Description: django-filter is a generic system for filtering Django QuerySets based on user selections. In django-filter before version 2.4.0, automatically generated `NumberFilter` instances, whose value was later converted to an integer, were subject to potential DoS from maliciously input using exponential format with sufficiently large exponents. Version 2.4.0+ applies a `MaxValueValidator` with a a default `limit_value` of 1e50 to the form
iently large exponents. Version 2.4.0+ applies a `MaxValueValidator` with a a default `limit_value` of 1e50 to the form field used by `NumberFilter` instances. In addition, `NumberFilter` implements the new `get_max_validator()` which should return a configured validator instance to customise the limit, or else `None` to disable the additional validation. Users may manually apply an equivalent validator if they are not able to upgrade. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/carltongibson/django-filter/security/advisories/GHSA-x7gm-rfgv-w973 - https://github.com/carltongibson/django-filter/commit/340cf7a23a2b3dcd7183f6a0d6c383e85b130d2b - https://g
m-rfgv-w973 - https://github.com/carltongibson/django-filter/commit/340cf7a23a2b3dcd7183f6a0d6c383e85b130d2b - https://github.com/carltongibson/django-filter/releases/tag/2.4.0 - https://pypi.org/project/django-filter/ - https://security.netapp.com/advisory/ntap-20210604-0010/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DPHENTRHRAYFXYPPBT7JRHZRWILRY44S/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FAT2ZAEF6DM3VFSOHKB7X3ASSHGQHJAK/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SVJ7AYU6FUSU3F653YCGW5LFD3IULRSX/
CVE ID: CVE-2020-15226 State: PUBLISHED Published: 2020-10-07T19:20:14 Last Updated: 2024-08-04T13:08:22.889Z Severity: MEDIUM (CVSS 5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N) Vendors: glpi-project Products: glpi Problem Types: CWE-89 Description: In GLPI before version 9.5.2, there is a SQL Injection in the API's search function. Not only is it possible to break the SQL syntax, but it is also possible to utilise a UNION SELECT query to reflect sensitive information such as the current database version, or database user. The most likely scenario for this vulnerability is with someone who has an API account to the system. The issue is patched in version 9.5.2. A proof-of-concept with tec
is with someone who has an API account to the system. The issue is patched in version 9.5.2. A proof-of-concept with technical details is available in the linked advisory. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/security/advisories/GHSA-jwpv-7m4h-5gvc - https://github.com/glpi-project/glpi/commit/3dc4475c56b241ad659cc5c7cb5fb65727409cf0
CVE ID: CVE-2020-15227 State: PUBLISHED Published: 2020-10-01T19:00:19 Last Updated: 2024-08-04T13:08:22.829Z Severity: HIGH (CVSS 8.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) Vendors: nette Products: application Problem Types: CWE-74 Description: Nette versions before 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, 3.0.6 are vulnerable to an code injection attack by passing specially formed parameters to URL that may possibly leading to RCE. Nette is a PHP/Composer MVC Framework. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/nette/application/security/advisories/GHSA-8gv3-3j7f-wg94 - https://packagist.org/packages/nette/application - https://packagist.org/