Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2020-15092 State: PUBLISHED Published: 2020-07-09T18:25:12 Last Updated: 2024-08-04T13:08:21.479Z Severity: HIGH (CVSS 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) Vendors: NUKnightLab Products: TimelineJS3 Problem Types: CWE-79 Description: In TimelineJS before version 3.7.0, some user data renders as HTML. An attacker could implement an XSS exploit with maliciously crafted content in a number of data fields. This risk is present whether the source data for the timeline is stored on Google Sheets or in a JSON configuration file. Most TimelineJS users configure their timeline with a Google Sheets document. Those users are exposed to this vulnerability if they grant write acc
gure their timeline with a Google Sheets document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if they grant public write access to the document. Some TimelineJS users configure their timeline with a JSON document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if write access to the system hosting that document is otherwise compromised. Version 3.7.0 of TimelineJS addresses this in two ways. For content which is intended to support limited HT
compromised. Version 3.7.0 of TimelineJS addresses this in two ways. For content which is intended to support limited HTML markup for styling and linking, that content is "sanitized" before being added to the DOM. For content intended for simple text display, all markup is stripped. Very few users of TimelineJS actually install the TimelineJS code on their server. Most users publish a timeline using a URL hosted on systems we control. The fix for this issue is published to our system such that **those users will automatically begin using the new code**. The only exception would be users who have deliberately edited the embed URL to "pin" their timeline to an earlier version of the code. Some
ould be users who have deliberately edited the embed URL to "pin" their timeline to an earlier version of the code. Some users of TimelineJS use it as a part of a wordpress plugin (knight-lab-timelinejs). Version 3.7.0.0 of that plugin and newer integrate the updated code. Users are encouraged to update the plugin rather than manually update the embedded version of TimelineJS. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/NUKnightLab/TimelineJS3/security/advisories/GHSA-2jpm-827p-j44g - https://knightlab.northwestern.edu/posts/
CVE ID: CVE-2020-15093 State: PUBLISHED Published: 2020-07-09T18:45:16 Last Updated: 2024-08-04T13:08:21.663Z Severity: HIGH (CVSS 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N) Vendors: awslabs Products: tough Problem Types: CWE-347 Description: The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is considered valid. A fix is available in version 0.7.1. CVE-2020-6174 is assigned to the same vulnerability in the TUF reference implementation. Additional Analyst Notes:
7.1. CVE-2020-6174 is assigned to the same vulnerability in the TUF reference implementation. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/awslabs/tough/security/advisories/GHSA-5q2r-92f9-4m49 - https://crates.io/crates/tough - https://github.com/theupdateframework/tuf/pull/974 - https://github.com/theupdateframework/tuf/commit/2977188139d065ff3356c3cb4aec60c582b57e0e
CVE ID: CVE-2020-15094 State: PUBLISHED Published: 2020-09-02T17:35:15 Last Updated: 2024-08-04T13:08:22.072Z Severity: HIGH (CVSS 8 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H) Vendors: symfony Products: symfony Problem Types: CWE-212 Description: In Symfony before versions 4.4.13 and 5.1.5, the CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient
nd ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible. This has been fixed in versions 4.4.13 and 5.1.5. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/symfony/symfony/security/advisories/GHSA-754h-5r27-7x3r - https://github.com/symfony/symfony/commit/d9910e0b33a2e0f993abff41c6fbc86951b66d78 - https://packagist.org/packages/symfony/symfony - https://packagist.org/packages/symfony/http-kernel - https://lists.fedoraproject.org/archives/list/package-announce%40lists
ps://packagist.org/packages/symfony/http-kernel - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VAQJXAKWPMWB7OL6QPG2ZSEQZYYPU5RC/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HNGUWOEETOFVH4PN3I3YO4QZHQ4AUKF3/
CVE ID: CVE-2020-15095 State: PUBLISHED Published: 2020-07-07T18:55:12 Last Updated: 2024-08-04T13:08:21.646Z Severity: MEDIUM (CVSS 4.4 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N) Vendors: npm Products: cli Problem Types: CWE-532 Description: Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>". The password value is not redacted and is printed to stdout and also to any generated log files. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp - https://git
- CVE Program Container: References: - https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp - https://github.com/npm/cli/commit/a9857b8f6869451ff058789c4631fadfde5bbcbc - https://github.com/npm/cli/blob/66aab417f836a901f8afb265251f761bb0422463/CHANGELOG.md#6146-2020-07-07 - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00011.html - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00015.html - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00023.html - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/ - https://security.gentoo.org/glsa/202101-07
CVE ID: CVE-2020-15096 State: PUBLISHED Published: 2020-07-07T00:10:13 Last Updated: 2024-08-04T13:08:22.273Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N) Vendors: electron Products: electron Problem Types: CWE-501 Description: In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there 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 privileged actions. Apps using "contextIsolation" are affected. There are no app-side workarounds, you must update your Electron version to be protected. This is fixed in versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta
ds, you must update your Electron version to be protected. This is fixed in versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21. Additional Analyst Notes: - CVE Program Container: References: - https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824 - https://github.com/electron/electron/security/advisories/GHSA-6vrv-94jv-crrg
CVE ID: CVE-2020-15097 State: PUBLISHED Published: 2021-02-02T17:35:13 Last Updated: 2024-08-04T13:08:21.765Z Severity: CRITICAL (CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) Vendors: loklak Products: loklak Problem Types: CWE-22 Description: loklak is an open-source server application which is able to collect messages from various sources, including twitter. The server contains a search index and a peer-to-peer index sharing interface. All messages are stored in an elasticsearch index. In loklak less than or equal to commit 5f48476, a path traversal vulnerability exists. Insufficient input validation in the APIs exposed by the loklak server allowed a directory traversal vulnerabil
exists. Insufficient input validation in the APIs exposed by the loklak server allowed a directory traversal vulnerability. Any admin configuration and files readable by the app available on the hosted file system can be retrieved by the attacker. Furthermore, user-controlled content could be written to any admin config and files readable by the application. This has been patched in commit 50dd692. Users will need to upgrade their hosted instances of loklak to not be vulnerable to this exploit. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/loklak/loklak_server/security/advisories/GHSA-7557-4v29-rqw6 - https://github.com/loklak/loklak_server/commit/50dd6
.com/loklak/loklak_server/security/advisories/GHSA-7557-4v29-rqw6 - https://github.com/loklak/loklak_server/commit/50dd69230d3cd71dab0bfa7156682ffeca8ed8b9
CVE ID: CVE-2020-15098 State: PUBLISHED Published: 2020-07-29T16:15:25 Last Updated: 2024-08-04T13:08:21.790Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: TYPO3 Products: TYPO3 CMS Problem Types: CWE-325, CWE-20, CWE-200, CWE-502 Description: In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, inse
age authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, insecure deserialization & remote code execution. The overall severity of this vulnerability is high based on mentioned attack chains and the requirement of having a valid backend user session (authenticated). This has been patched in versions 9.5.20 and 10.4.6. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-m5vr-3m74-jwxp - https://typo3.org/security/advisory/typo3-core-sa-2016-013 - https://typo3.org/security/advisory/typo3-core-sa-2020-008 - https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99
- https://typo3.org/security/advisory/typo3-core-sa-2020-008 - https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1
CVE ID: CVE-2020-15099 State: PUBLISHED Published: 2020-07-29T16:15:15 Last Updated: 2024-08-04T13:08:22.299Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: TYPO3 Products: TYPO3 CMS Problem Types: CWE-200, CWE-20 Description: In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6, in a case where an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal encryptionKey was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to
nKey was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch typo3conf/LocalConfiguration.php, which again contains the encryptionKey as well as credentials of the database management system being used. In case a database server is directly accessible either via internet or in a shared hosting network, this allows the ability to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions. This has been patched in versions 9.5.20 and 10.4.6. Additional Analyst Notes: - CVE Program Container:
tom extensions. This has been patched in versions 9.5.20 and 10.4.6. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-3x94-fv5h-5q2c - https://typo3.org/security/advisory/typo3-core-sa-2020-007
CVE ID: CVE-2020-15100 State: PUBLISHED Published: 2020-07-14T19:15:16 Last Updated: 2024-08-04T13:08:21.992Z Severity: LOW (CVSS 2.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L) Vendors: schokokeksorg Products: freewvs Problem Types: CWE-400 Description: In freewvs before 0.1.1, a user could create a large file that freewvs will try to read, which will terminate a scan process. This has been patched in 0.1.1. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/schokokeksorg/freewvs/security/advisories/GHSA-9cfv-9463-8gqv - https://github.com/schokokeksorg/freewvs/commit/18bbf2043e53f69e0119d24f8ae4edb274afb9b2
CVE ID: CVE-2020-15101 State: PUBLISHED Published: 2020-07-14T21:35:12 Last Updated: 2024-08-04T13:08:21.765Z Severity: LOW (CVSS 2.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L) Vendors: schokokeksorg Products: freewvs Problem Types: CWE-400 Description: In freewvs before 0.1.1, a directory structure of more than 1000 nested directories can interrupt a freewvs scan due to Python's recursion limit and os.walk(). This can be problematic in a case where an administrator scans the dirs of potentially untrusted users. This has been patched in 0.1.1. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/schokokeksorg/freewvs/security/advisories/GHSA-7pmh-vrww-25xx -
CVE Program Container: References: - https://github.com/schokokeksorg/freewvs/security/advisories/GHSA-7pmh-vrww-25xx - https://github.com/schokokeksorg/freewvs/commit/83a6b55c0435c69f447488b791555e6078803143
CVE ID: CVE-2020-15102 State: PUBLISHED Published: 2020-07-21T17:50:12 Last Updated: 2024-08-04T13:08:21.786Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) Vendors: PrestaShop Products: dashproducts Problem Types: CWE-284 Description: In PrestaShop Dashboard Productions before version 2.1.0, there is improper authorization which enables an attacker to change the configuration. The problem is fixed in 2.1.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/PrestaShop/dashproducts/security/advisories/GHSA-6292-4qpg-hvfg - https://github.com/PrestaShop/dashproducts/commit/f0799c13628a9b9ca6ca75c085b083d924a8ea7e
CVE ID: CVE-2020-15103 State: PUBLISHED Published: 2020-07-27T00:00:00 Last Updated: 2024-08-04T13:08:21.774Z Severity: LOW (CVSS 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L) Vendors: FreeRDP Products: FreeRDP Problem Types: CWE-680 Description: In FreeRDP less than or equal to 2.1.2, an integer overflow exists due to missing input sanitation in rdpegfx channel. All FreeRDP clients are affected. The input rectangles from the server are not checked against local surface coordinates and blindly accepted. A malicious server can send data that will crash the client later on (invalid length arguments to a `memcpy`) This has been fixed in 2.2.0. As a workaround, stop using command line argume
n (invalid length arguments to a `memcpy`) This has been fixed in 2.2.0. As a workaround, stop using command line arguments /gfx, /gfx-h264 and /network:auto Additional Analyst Notes: - CVE Program Container: References: - https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-4r38-6hq7-j3j9 - https://github.com/FreeRDP/FreeRDP/blob/616af2d5b86dc24c7b3e89870dbcffd841d9a535/ChangeLog#L4 - https://github.com/FreeRDP/FreeRDP/pull/6382 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6Y35HBHG2INICLSGCIKNAR7GCXEHQACQ/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XOZLH35OJWIQLM7FYDXAP2EAUBD
s://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XOZLH35OJWIQLM7FYDXAP2EAUBDXE76V/ - http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00010.html - https://usn.ubuntu.com/4481-1/ - https://lists.debian.org/debian-lts-announce/2023/10/msg00008.html
CVE ID: CVE-2020-15104 State: PUBLISHED Published: 2020-07-14T22:05:14 Last Updated: 2024-08-04T13:08:22.235Z Severity: MEDIUM (CVSS 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) Vendors: envoyproxy Products: envoy Problem Types: CWE-346 Description: In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS
domain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This vulnerability is only applicable to situations where an untrusted entity can obtain a signed wildcard TLS certificate for a domain of which you only intend to trust a subdomain of. For example, if you intend to trust api.mysubdomain.example.com, and an untrusted actor can obtain a signed TLS certificate for *.example.com or *.com. Configurations are vulnerable if they use verify_subject_alt_name in any Envoy version, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6
ion, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6, 1.13.4, 1.14.4, 1.15.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg
CVE ID: CVE-2020-15105 State: PUBLISHED Published: 2020-07-10T20:55:13 Last Updated: 2024-08-04T13:08:21.577Z Severity: MEDIUM (CVSS 5.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N) Vendors: Bouke Products: django-two-factor-auth Problem Types: CWE-312 Description: Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever
means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password and then leaves before entering their two-factor authentication code. The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' passwords are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache se
sswords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' passwords are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis). This has been fixed in 1.12. After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas. In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that
ffected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used. As a workaround, wwitching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading. Additional Analyst Notes: - CVE Pro
side session storage. There is no way to fully mitigate the issue without upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf - https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359 - https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08
CVE ID: CVE-2020-15106 State: PUBLISHED Published: 2020-08-05T19:05:13 Last Updated: 2024-08-04T13:08:21.619Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Vendors: etcd-io Products: etcd Problem Types: CWE-20 Description: In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic in decodeRecord method. The size of a record is stored in the length field of a WAL file and no additional validation is done on this data. Therefore, it is possible to forge an extremely large frame size that can unintentionally panic at the expense of any RAFT participant trying to decode the WAL. Additional Analyst Notes: - CVE Program Container: References: - https://github
FT participant trying to decode the WAL. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/etcd-io/etcd/security/advisories/GHSA-p4g4-wgrh-qrg2 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L6B6R43Y7M3DCHWK3L3UVGE2K6WWECMP/
CVE ID: CVE-2020-15107 State: PUBLISHED Published: 2020-07-15T21:21:38 Last Updated: 2024-08-04T13:08:21.928Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:N) Vendors: openenclave Products: openenclave Problem Types: Compromised execution integrity Description: In openenclave before 0.10.0, enclaves that use x87 FPU operations are vulnerable to tampering by a malicious host application. By violating the Linux System V Application Binary Interface (ABI) for such operations, a host app can compromise the execution integrity of some x87 FPU operations in an enclave. Depending on the FPU control configuration of the enclave app and whether the operations are used in secre
n an enclave. Depending on the FPU control configuration of the enclave app and whether the operations are used in secret-dependent execution paths, this vulnerability may also be used to mount a side-channel attack on the enclave. This has been fixed in 0.10.0 and the current master branch. Users will need 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-7wjx-wcwg-w999